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. The supported Cisco TelePresence MCUs are:
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. The supported Cisco TelePresence MCUs are:
n
Cisco TelePresence MCU
n
Cisco TelePresence Server
n
Cisco TelePresence MPS
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 always uses the same numbers for all
recurrences.
(SIP URI/H.323 ID/E.164 alias). For recurrent bookings Cisco TMS always uses the same numbers for all
recurrences.
You can specify what type of MCU Cisco TMS will use as default 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. 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. Otherwise any MCU can be chosen by
Cisco TMS.
When booking using TMS Scheduler and the booking API it is not possible to change the default conference
settings set in
settings set in
Administrative Tools > Configuration > Conference Settings
. To make MCU choices
and implement cascading you need to use TMS booking via
Booking > New Conference
.
Cisco TelePresence Conductor
If using a Cisco TelePresence Conductor in front of your MCUs, Cisco TMS lets the Conductor decide which
MCU(s) to use in a conference.
MCU(s) to use in a conference.
ISDN Gateway
An ISDN gateway allows an IP network to call out to ISDN and ISDN to call into an IP network.
Your gateway does not need to be added into Cisco TMS, you simply add gateway information to your IP
zone so that Cisco TMS knows what prefix systems in that zone should dial for ISDN. (See
zone so that Cisco TMS knows what prefix systems in that zone should dial for ISDN. (See
).
Extended settings DID mapping for Cisco TelePresence MCUs
In the settings for a Cisco TelePresence MCU in Cisco TMS you can implement Direct Inbound Dial (DID)
mapping to create a list of DID numbers that Cisco TMS can use as ISDN dial ins for scheduled
conferences. Cisco TMS matches the numbers up with the E.164 aliases already set up for conferences on
mapping to create a list of DID numbers that Cisco TMS can use as ISDN dial ins for scheduled
conferences. Cisco TMS matches the numbers up with the E.164 aliases already set up for conferences on
Cisco TMS Administrator Guide (14.1)
Page 36 of 320
Routing
What infrastructure does Cisco TMS use for routing?