Configuration Guide for Cisco Unified Videoconferencing Manager Release 5.7 - Defining Resource Manager Call Routing Modes [Cisco Unified Videoconferencing Manager]

Table Of Contents

Defining Resource Manager Call Routing Modes

Call Routing in H.323 Deployments

Call Routing in SIP Deployments

Masking Conference Topology with the Virtual MCU Feature

Creating a Centralized Conference

Creating a Distributed Conference

Defining Resource Manager Call Routing Modes

Resource Manager offers two call routing modes. This section describes these modes and explains their use in H.323 and SIP deployments.

•Call Routing in H.323 Deployments

•Call Routing in SIP Deployments

•Masking Conference Topology with the Virtual MCU Feature

Call Routing in H.323 Deployments

In Fully Routed H.323 Mode, Resource Manager acts as an authorization server to the internal gatekeeper. Resource Manager manages all traffic passing through the internal gatekeeper and can control where incoming calls will go.

Fully Routed Mode enables the "Virtual MCU" feature where Resource Manager can present multiple MCUs as a single pool of video and audio ports, or as a single virtual MCU.

For Fully Routed Mode, ensure you select the Enable Gatekeeper advanced features (authorization and point-to-point) option.

Procedure

Step 1 Click Resource Management in the sidebar menu.

Step 2 Click Gatekeeper/SIP server.

Step 3 Click the link in the Name column for the gatekeeper you require, or click Add to create a new gatekeeper profile.

Step 4 Locate the Advanced section.

The Advanced section appears if you are using the internal gatekeeper.

Step 5 Select Enable Gatekeeper advanced features (authorization and point-to-point).

Step 6 Click OK to save your changes.

Call Routing in SIP Deployments

In SIP deployments, Resource Manager works in Fully Routed Mode using the embedded SIP server to manage all traffic.

Because MCUs have Resource Manager configured as the outbound proxy, and the external SIP server is configured to route incoming calls to the Resource Manager embedded SIP server, Resource Manager can control all calls going through the MCU.

Note Resource Manager cannot manage SIP endpoint point-to-point traffic because these endpoints are registered to the external SIP server.

Masking Conference Topology with the Virtual MCU Feature

By controlling the call routing logic of the internal gatekeeper, Resource Manager can mask the complexity of the actual network deployment from end users. Resource Manager can create a conference that spans multiple MCUs and present the conference to the end user as a single conference with a single dialing ID, a single PIN, and a single In-meeting Control interface to manage it. This is the Resource Manager Virtual MCU feature.

Creating a Centralized Conference

Procedure

Step 1 Under Admin > Advanced Settings > Default Meeting Settings, set the Prioritize field to Delay to host a conference on a single MCU when possible.

Resource Manager cascades multiple MCUs to create a conference only if the conference size is larger than the capacity of a single MCU.

Step 2 Click OK to save your changes.

Creating a Distributed Conference

Procedure

Step 1 Under Admin > Advanced Settings > Default Meeting Settings, set the Prioritize field to Local MCU to force endpoints to cascade to their local MCU first, according to the IP topology configured in the Network Management section.

If there are endpoints from multiple locations, at least one MCU from each location is cascaded into the main MCU conference.

Step 2 Click OK to save your changes.

	Configuration Guide for Cisco Unified Videoconferencing Manager Release 5.7
	Defining Resource Manager Call Routing Modes
Configuration Guide for Cisco Unified Videoconferencing Manager Release 5.7 Part 1. Resource Manager Managing Network Topologies in Resource Manager Configuring a Gatekeeper Profile in Resource Manager Configuring a SIP Server Profile in Resource Manager Managing an MCU Profile in Resource Manager Configuring a Gateway Profile in Resource Manager Configuring a Cisco Unified Videoconferencing Desktop Server Profile in Resource Manager Configuring a Meeting Room Profile in Resource Manager Configuring a Terminal Profile in Resource Manager Defining Resource Manager Call Routing Modes Managing Resource Manager Users and User Groups without an External Directory Provisioning Resource Manager Users via a Directory Server Viewing Meeting Schedules in Resource Manager Modifying Default Organization Settings for Resource Manager Users and Meetings Using the Resource Manager Configuration Tool Resource Manager CDR XML Tags and Attributes Enabling Resource Manager to Use Secure Sockets Layer Connections on a JBoss Application Server Network Manager Viewing Your Network in Network Manager Managing Elements in Network Manager Managing Endpoints in Network Manager Managing the Internal Gatekeeper in Network Manager Managing an MCU in Network Manager Managing a Gateway in Network Manager Configuring a User Profile in Network Manager Managing Traps and Alarms in Network Manager Managing Calls and Conferences in Network Manager Configuring Logging for Network Manager Part 3. Desktop Cisco Unified Videoconferencing Desktop Features Configuring Cisco Unified Videoconferencing Desktop Index	Download this chapter Defining Resource Manager Call Routing Modes Download the complete book Configuration Guide for Cisco Unified Videoconferencing Manager Release 5.7 (PDF - 2 MB) Table Of Contents Defining Resource Manager Call Routing Modes Call Routing in H.323 Deployments Call Routing in SIP Deployments Masking Conference Topology with the Virtual MCU Feature Creating a Centralized Conference Creating a Distributed Conference Defining Resource Manager Call Routing Modes Resource Manager offers two call routing modes. This section describes these modes and explains their use in H.323 and SIP deployments. •Call Routing in H.323 Deployments •Call Routing in SIP Deployments •Masking Conference Topology with the Virtual MCU Feature Call Routing in H.323 Deployments In Fully Routed H.323 Mode, Resource Manager acts as an authorization server to the internal gatekeeper. Resource Manager manages all traffic passing through the internal gatekeeper and can control where incoming calls will go. Fully Routed Mode enables the "Virtual MCU" feature where Resource Manager can present multiple MCUs as a single pool of video and audio ports, or as a single virtual MCU. For Fully Routed Mode, ensure you select the Enable Gatekeeper advanced features (authorization and point-to-point) option. Procedure Step 1 Click Resource Management in the sidebar menu. Step 2 Click Gatekeeper/SIP server. Step 3 Click the link in the Name column for the gatekeeper you require, or click Add to create a new gatekeeper profile. Step 4 Locate the Advanced section. The Advanced section appears if you are using the internal gatekeeper. Step 5 Select Enable Gatekeeper advanced features (authorization and point-to-point). Step 6 Click OK to save your changes. Call Routing in SIP Deployments In SIP deployments, Resource Manager works in Fully Routed Mode using the embedded SIP server to manage all traffic. Because MCUs have Resource Manager configured as the outbound proxy, and the external SIP server is configured to route incoming calls to the Resource Manager embedded SIP server, Resource Manager can control all calls going through the MCU. Note Resource Manager cannot manage SIP endpoint point-to-point traffic because these endpoints are registered to the external SIP server. Masking Conference Topology with the Virtual MCU Feature By controlling the call routing logic of the internal gatekeeper, Resource Manager can mask the complexity of the actual network deployment from end users. Resource Manager can create a conference that spans multiple MCUs and present the conference to the end user as a single conference with a single dialing ID, a single PIN, and a single In-meeting Control interface to manage it. This is the Resource Manager Virtual MCU feature. Creating a Centralized Conference Procedure Step 1 Under Admin > Advanced Settings > Default Meeting Settings, set the Prioritize field to Delay to host a conference on a single MCU when possible. Resource Manager cascades multiple MCUs to create a conference only if the conference size is larger than the capacity of a single MCU. Step 2 Click OK to save your changes. Creating a Distributed Conference Procedure Step 1 Under Admin > Advanced Settings > Default Meeting Settings, set the Prioritize field to Local MCU to force endpoints to cascade to their local MCU first, according to the IP topology configured in the Network Management section. If there are endpoints from multiple locations, at least one MCU from each location is cascaded into the main MCU conference. Step 2 Click OK to save your changes.
	© 1992-2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.