Cisco Cisco TelePresence MCU 4510 Installation Guide
dynamic escalation can only be initiated by endpoints that support the configuration of a conference button
which is used to escalate the call.
which is used to escalate the call.
Rendezvous conferences
Rendezvous conferences on an MCU are those that a participant can join at any time. These conferences
can be configured for individual use, or for communal first-come, first-served conferences.
can be configured for individual use, or for communal first-come, first-served conferences.
Rendezvous conferences can be statically configured on an MCU by defining a conference room on the
device. It is also possible to dynamically create a conference room so that no pre-configuration is required.
Statically configured conferences allow unique settings to be set per conference, whilst dynamic
conferences must follow a single template.
device. It is also possible to dynamically create a conference room so that no pre-configuration is required.
Statically configured conferences allow unique settings to be set per conference, whilst dynamic
conferences must follow a single template.
When using the MCU with Cisco VCS but not TelePresence Conductor, static conferences must be defined
on individual MCUs and therefore are vulnerable to a single point of failure.
on individual MCUs and therefore are vulnerable to a single point of failure.
When using Conductor, Rendezvous conferences are configured on the TelePresence Conductor; therefore
the conference is never statically defined on a single MCU. This increases conference resilience while
maintaining the ability to have unique conference settings.
the conference is never statically defined on a single MCU. This increases conference resilience while
maintaining the ability to have unique conference settings.
These conferences can be configured in a similar way to an MCU registered to Cisco VCS or trunked to
Unified CM, either by predefining the conference number and configuration or by allowing the MCU to
dynamically create the conference.
Unified CM, either by predefining the conference number and configuration or by allowing the MCU to
dynamically create the conference.
Network topology
An MCU causes a concentration of video traffic at its location because each port can have a video call
connected to it at up to 4Mbit/s (plus IP overhead, typically 20%). Therefore, MCUs should be placed at a
network location that has enough bandwidth to host these calls.
connected to it at up to 4Mbit/s (plus IP overhead, typically 20%). Therefore, MCUs should be placed at a
network location that has enough bandwidth to host these calls.
We recommend that MCUs be placed on the internal network with firewall protection from outside access.
For external calling, a Cisco VCS Expressway should be used in conjunction with a Cisco VCS Control in
order to allow video calls to traverse the firewall.
For external calling, a Cisco VCS Expressway should be used in conjunction with a Cisco VCS Control in
order to allow video calls to traverse the firewall.
If the second Ethernet port is activated (on the MCU 4500 and 5300 series this requires the Video Firewall
Option key). Cisco recommends that this port is also connected to an internal network and used for purposes
such as separating MCU management traffic from MCU video traffic.
Option key). Cisco recommends that this port is also connected to an internal network and used for purposes
such as separating MCU management traffic from MCU video traffic.
Baseline configuration
Some MCU settings are independent of the MCU deployment but can affect the quality experienced. The
table below lists the most important of these and the value assumed for the deployments in this guide:
table below lists the most important of these and the value assumed for the deployments in this guide:
MCU Setting
Recommended
Maximum video size
Receive Max, transmit Max
Table 2: Recommended Baseline MCU settings
Cisco TelePresence MCU Deployment Guide 4.4
Page 7 of 53
Background