Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
What infrastructure does Cisco TMS use for
routing?
routing?
MCU
An MCU (Multipoint Control Unit) is a conference bridge that can host a number of conferences at the same
time depending on its port allocation. Participants can dial in, or the MCU can dial out to them. Cisco TMS
supports many different models of MCU. In a modern Cisco TelePresence deployment we recommend the
following for optimum performance:
time depending on its port allocation. Participants can dial in, or the MCU can dial out to them. Cisco TMS
supports many different models of MCU. In a modern Cisco TelePresence deployment we recommend the
following for optimum performance:
n
Cisco TelePresence MCU Series
n
Cisco TelePresence Server
Note that Cisco TMS gives each MCU port a number (starting at 1 for the first port and so on), and an alias
(SIP URI/H.323 ID/E.164 alias). For recurrent bookings Cisco TMS uses the same port number and alias for
all recurrences.
(SIP URI/H.323 ID/E.164 alias). For recurrent bookings Cisco TMS uses the same port number and alias for
all recurrences.
You can specify what type of MCU Cisco TMS will prefer in scheduled conferences here:
Administrative
Tools > Configuration > Conference Settings >
Preferred MCU Type in Routing.
You can specify when the MCU should be used in routing here:
Administrative Tools > Configuration >
Conference Settings >
External MCU Usage in Routing.
If you have several similar MCUs in Cisco TMS, the MCU will be selected based on which zone the
conference participants belong to, and the capability set of the systems in the conference: conferences
including immersive systems will use a Cisco TelePresence Server if available. Otherwise any MCU can be
chosen by Cisco TMS.
conference participants belong to, and the capability set of the systems in the conference: conferences
including immersive systems will use a Cisco TelePresence Server if available. Otherwise any MCU can be
chosen by Cisco TMS.
Note that a directly managed MCU must be registered to an H.323 gatekeeper or SIP registrar for Cisco TMS
to be able to schedule it. For example, scheduling of SIP-trunked bridges is not supported in Cisco TMS.
to be able to schedule it. For example, scheduling of SIP-trunked bridges is not supported in Cisco TMS.
When booking using any extension that relies on Cisco TMSBA, including Smart Scheduler, it is not possible
to change the default conference settings in
to change the default conference settings in
Administrative Tools > Configuration > Conference
Settings
.
Distribution
Administrators can configure Cisco TMS to calculate routing across several MCUs either to reduce cost
and/or bandwidth, or to achieve the highest quality. This is known as cascading. See
and/or bandwidth, or to achieve the highest quality. This is known as cascading. See
When Cisco TMS cannot fit all participants onto one MCU, the user is informed with an error during booking,
as cascading does not happen automatically. The user must then choose between either Best Impression or
Least Cost distribution, to cascade the call over two or more MCUs. For this reason cascading is only
possible when booking using the Cisco TMS booking interface, it is not possible to cascade using the Cisco
TMSBA.
as cascading does not happen automatically. The user must then choose between either Best Impression or
Least Cost distribution, to cascade the call over two or more MCUs. For this reason cascading is only
possible when booking using the Cisco TMS booking interface, it is not possible to cascade using the Cisco
TMSBA.
Note that the setting
Administrative Tools > Configuration > Conference Settings >
Preferred MCU
Type in Routing is ignored when it comes to distribution.
Not all MCUs are supported for use in cascading: for example the TelePresence Server.
Cisco TMS Administrator Guide (14.3)
Page 44 of 340
Routing
What infrastructure does Cisco TMS use for routing?