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 the following types of MCU:
time depending on its port allocation. Participants can dial in, or the MCU can dial out to them. Cisco TMS
supports the following types of MCU:
n
Cisco TelePresence Server
n
Cisco TelePresence MCU Series
n
Cisco TelePresence MPS
n
Unmanaged bridge
For new telepresence deployments, we recommend using TelePresence Server for optimum performance.
You can specify what type of MCUCisco 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 or an unmanaged bridge configured as
Immersive, 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 or an unmanaged bridge configured as
Immersive, if available. Otherwise any MCU can be chosen by Cisco TMS.
Cisco TMS supports both scheduling of SIP-trunked bridges and bridges registered to an H.323 gatekeeper
or SIP registrar.
or SIP registrar.
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
.
Number allocation
When routing a conference, Cisco TMS tries to use the lowest possible number or alias in the assigned range
as follows:
as follows:
1. Cisco TMS tries to find an unused number or alias on a bridge within a 4 hour window around the
conference (4 hours before the start time and 4 hours after the end time).
2. If there are no unused numbers or aliases during that time frame, Cisco TMS tries a 2 hour window, then 1
hour, 45 minutes, 30 minutes, 15 minutes, and finally settles on a number or alias that is unique for the
exact duration of the conference.
exact duration of the conference.
This is so that back-to-back meetings are not allocated with the same number or alias unless no other
number is available, so participants are not at risk of dialing into the previous conference.
number is available, so participants are not at risk of dialing into the previous conference.
For recurrent bookings Cisco TMS uses the same number or alias for all occurrences.
This also applies to bridges behind TelePresence Conductor if variable alias patterns are used.
Cisco TelePresence Management Suite Administrator Guide (14.5)
Page 41 of 340
Routing
What infrastructure does Cisco TMS use for routing?