Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
What Infrastructure Does Cisco TMS Use for Routing?
MCU
An MCU (Multipoint Control Unit) is a conference bridge that can host a number of conferences at the same time depend-
ing on its port allocation. Participants can dial in, or the MCU can dial out to them. Cisco TMS supports the following
types of MCU:
ing on its port allocation. Participants can dial in, or the MCU can dial out to them. Cisco TMS supports the following
types of MCU:
■
Cisco TelePresence Server
■
Cisco TelePresence MCU Series
■
Cisco TelePresence MPS
■
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 > Con-
figuration > Conference Settings >
Preferred MCU Type in Routing.
You can specify when the MCU should be used in routing here:
Administrative Tools > Configuration > Conference Set-
tings >
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 par-
ticipants 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.
ticipants 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 regis-
trar.
trar.
When booking using any extension that relies on Cisco TMSBA, including Smart Scheduler, it is not possible to change
the default conference settings in
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:
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).
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.
45 minutes, 30 minutes, 15 minutes, and finally settles on a number or alias that is unique for the 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 avail-
able, so participants are not at risk of dialing into the previous conference.
able, 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.
Managed MCUs Only
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). The first number and the step are configurable for each MCU in
ID/E.164 alias). The first number and the step are configurable for each MCU in
Extended Settings
. For recurrent book-
ings Cisco TMS uses the same port number for all occurrences.
Cisco TMS reads the number of ports from the bridge, it is not aware of whether it is SD or HD quality.To differentiate in
this way we recommend using a TelePresence Conductor.
this way we recommend using a TelePresence Conductor.
25
Cisco TelePresence Management Suite Administrator Guide
Routing