Design Guide for the Cisco Unified Videoconferencing Solution Using Desktop Component Release 5.5
Selecting a Cisco Unified Videoconferencing Solution Deployment Topology

Table Of Contents

Selecting a Cisco Unified Videoconferencing Solution Deployment Topology

About Cisco Unified Videoconferencing Solution Deployments

About a Basic Deployment of the Cisco Unified Videoconferencing Solution

About Functionality of a Basic Deployment

About Limitations of a Basic Deployment

About a Small Centralized Deployment of the Cisco Unified Videoconferencing Solution

About Functionality of a Small Centralized Deployment

About Limitations of a Small Centralized Deployment

About a Large Centralized Deployment of the Cisco Unified Videoconferencing Solution

About Functionality of a Large Centralized Deployment

About Limitations of a Large Centralized Deployment


Selecting a Cisco Unified Videoconferencing Solution Deployment Topology


About Cisco Unified Videoconferencing Solution Deployments

About a Basic Deployment of the Cisco Unified Videoconferencing Solution

About a Small Centralized Deployment of the Cisco Unified Videoconferencing Solution

About a Large Centralized Deployment of the Cisco Unified Videoconferencing Solution

About Cisco Unified Videoconferencing Solution Deployments

Deployments described in this chapter suit installations of the Desktop component of the Cisco Unified Videoconferencing Manager using only a single network interface card (NIC). However, the Desktop technology is designed to also handle advanced topologies involving dual-NIC deployments, which are described in Appendix B, "Configuring Dual-NIC Deployments".

Deployments use these connections:

Tunneled—The normal UDP or TCP ports used for the media or control are not open in the complete path from Desktop Client to Desktop Server allowing you to use either a limited UDP port or a TCP port or just HTTP. The media is repacketized to accommodate the open connection; in some instances the media is made compatible with HTTP in order to tunnel through open ports or proxy servers. For the real time media this means:

For Desktop Client—SRTP/RTP/UDP traffic is tunneled through TCP or HTTP on port 80 or 443.

For Pathfinder—H.323 media and control traffic is tunneled through a simple UDP and TCP port combination instead of a wide range of UDP/TCP ports.

For streaming—TCP port 7070 or port 80 is used for web access and control (port 80, 443 or 8080).

For web access and conference control—TCP port 80, 443 or 8080 is used.

Untunneled—The normal port ranges of operation for UDP or TCP are opened so that the Desktop Client or Desktop Server can communicate without repackaging or redirecting to alternate ports or protocol (UDP to TCP or HTTP).

About a Basic Deployment of the Cisco Unified Videoconferencing Solution

This is the most basic deployment available if the Desktop Server uses a single NIC card. This deployment is particularly attractive for small and medium enterprises having a single main site. This topology contains these solution components:

Cisco Unified Videoconferencing Manager with the following components activated:

Desktop

Desktop Streaming Server

Cisco IOS H.323 Gatekeeper


Note All components are installed but only the above components are required for this type of deployment, and are activated.


Cisco Unified Videoconferencing 3500 Series MCU

The connection outside the enterprise is handled by the Desktop Client only.

Figure 1-1 Basic Deployment

Related Topics

About Functionality of a Basic Deployment

About Limitations of a Basic Deployment

About Functionality of a Basic Deployment

This solution supports conferences of up to 96 desktops or 72 room systems belonging to the same enterprise, depending on the capacity of the Cisco Unified Videoconferencing 3500 Series MCU model and configuration deployed. This deployment allows moderation of meetings using either the Desktop Client interface or the Conference Control interface of the Cisco Unified Videoconferencing 3500 Series MCU. The Desktop technology supports firewall and NAT traversal for Desktop connection via public networks.

To configure a firewall correctly for this deployment, see recommendations described in the "Configuring a Firewall" section on page 3-12.

About Limitations of a Basic Deployment

Since the Resource Manager component of the Cisco Unified Videoconferencing Manager is not activated in this topology, features such as virtual rooms, automatic MCU cascading and conference scheduling are not supported. This topology has only one MCU component; therefore, a conference cannot span multiple MCUs. In this case automatic cascading is not possible.

About a Small Centralized Deployment of the Cisco Unified Videoconferencing Solution

This deployment suits medium and large networks, and provides this functionality:

Uses a single Desktop Server together with multiple Cisco Unified Videoconferencing 3500 Series MCU components to connect desktop clients both inside and outside the corporate network.

Connects room systems inside a corporate network.

Conferencing solution for ISDN systems on the PSTN network using Cisco Unified Videoconferencing 3500 Series Gateways.

Uses the Resource Manager component to provide scheduling, resource reservation, virtual MCU scalability across multiple MCUs.

Figure 1-2 Small Centralized Deployment

This deployment typically includes these components:

Multiple Cisco Unified Videoconferencing 3500 Series MCU products—Located in the firewall-protected private network.

Desktop Server—Located in the firewall-protected DMZ.

Cisco Unified Videoconferencing Manager—Located in the firewall-protected DMZ. This component can be installed on the same server as Desktop or Cisco Streaming Server, or on separate dedicated servers for better performance and capacity.

Cisco IOS H.323 Gatekeeper—in the firewall-protected network.

Room videoconferencing systems

Cisco Unified Videoconferencing 3500 Series Gateways

ISDN videoconferencing endpoints on the PSTN/ISDN network

For this deployment, the Desktop and Streaming components of the Cisco Unified Videoconferencing Manager are typically installed on the same server as the Resource Manager component. The Cisco Unified Videoconferencing 3500 Series MCUs are located on the private network.

Related Topics

About Functionality of a Small Centralized Deployment

About Limitations of a Small Centralized Deployment

About Functionality of a Small Centralized Deployment

The Desktop Server resides in the DMZ. The deployment supports:

Desktop Clients both inside and outside the corporate network

Room systems inside the corporate network

Directory Server integration

Video conference scheduling via web or Microsoft Outlook

MCU resource reservation for scheduled conferences

Virtualization of multiple-MCU deployments for seamless scalability

Virtual rooms (reservationless personal video conference IDs)

ISDN systems on the PSTN/ISDN network

Supports up to 50 interactive Desktop connections and 150 live conference streams, simultaneously.

To configure a firewall correctly for this deployment, see recommendations described in "Configuring a Firewall" section on page 3-12.

About Limitations of a Small Centralized Deployment

Because all components of Cisco Unified Videoconferencing Manager are installed in a single server in the DMZ, the maximum capacity achievable on supported Cisco Media Convergence Servers (MCS) is 50 simultaneous Desktop client connections and 150 simultaneous live conference streams. See Table 3 in the Cisco Unified Videoconferencing Manager data sheet for details on supported Cisco MCS servers and their capacities: http://cisco.com/en/US/prod/collateral/video/ps7190/ps7088/product_data_sheet0900aecd8053684f.html

About a Large Centralized Deployment of the Cisco Unified Videoconferencing Solution

This deployment suits large enterprises providing:

Conferencing solution using multiple Desktop Servers together with multiple Cisco Unified Videoconferencing 3500 Series MCU components to provide scalable support of Desktop participants both inside and outside the corporate network.

Conferencing solution for room systems inside the corporate network using Cisco IOS H.323 Gatekeeper.

Conferencing solution for ISDN systems on the PSTN network using Cisco Unified Videoconferencing 3500 Series Gateways.

Figure 1-3 Large Centralized Deployment

This deployment typically includes these components:

Multiple Cisco Unified Videoconferencing 3500 Series MCU components—Located in the firewall-protected private network.

Cisco Unified Videoconferencing Manager components:

Desktop Servers—Multiple servers deployed in the firewall protected DMZ. The load from the Desktop participant connections is evenly distributed between the Desktop servers by a load balancer.

Streaming Server—Dedicated server for live streaming audience.

Resource and Network Manager Server—Providing the scheduling, resource reservations, virtualization of multiple MCUs, and network management of videoconferencing infrastructure.

Alternate Cisco IOS H.323 Gatekeeper—Located in the firewall-protected DMZ.

Cisco Unified Videoconferencing 3500 Series Gateway—Located on the firewall-protected private network.

Room (H.323, SIP, SCCP) videoconferencing endpoints

ISDN (H.320) videoconferencing endpoints on the PSTN/ISDN network

Related Topics

About Functionality of a Large Centralized Deployment

About Limitations of a Large Centralized Deployment

About Functionality of a Large Centralized Deployment

The deployment supports Desktop participants both inside and outside the corporate network, and room systems inside the corporate network. The deployment also supports ISDN systems on the PSTN/ISDN network. Cisco Unified Videoconferencing Manager provides scheduling, resource reservation, network management, support of Directory Server integration and virtual rooms (reservationless personal videoconferencing IDs).

This deployment supports up to 50 simultaneous Desktop participant connections per Desktop Server deployed. It also supports up to 300 simultaneous live conference streaming viewers on the dedicated Streaming Server.

To configure a firewall correctly for this deployment, see recommendations described in "Configuring a Firewall" section on page 3-12.

About Limitations of a Large Centralized Deployment

The deployment requires a load balancer.

The chat and `raise hand' Desktop participant features are not available in deployments with multiple Desktop Servers.