Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Routing
This chapter explains the methods used by Cisco TMS to route calls between systems using different protocols and net-
works, and how Cisco TMS selects network devices to optimize these connections.
works, and how Cisco TMS selects network devices to optimize these connections.
Before you can configure routing in Cisco TMS, you must have an overview of your telepresence network dial plan, and
which protocols and infrastructure your systems have in place.
which protocols and infrastructure your systems have in place.
Introduction to Routing
During the booking process, Cisco TMS tries to create a route between participants in a conference when one of the fol-
lowing actions takes place:
lowing actions takes place:
■
The user clicks Save Conference.
■
The user clicks the
Connection Settings
tab.
■
A Cisco TelePresence Management Suite Extension Booking API (Cisco TMSBA) client saves a conference.
When a conference is saved, corresponding dial-in numbers for the conference are distributed via email to the organizer
and/or participants. The route created by Cisco TMS is a suggestion and can be changed to another valid route during
booking by clicking on the
and/or participants. The route created by Cisco TMS is a suggestion and can be changed to another valid route during
booking by clicking on the
Connection Settings
tab. If Cisco TMS is unable to create a route between all participants, the
action fails, and an error is displayed. The administrator can then make changes, such as removing some participants, so
that a route can be created.
that a route can be created.
Whenever a conference is edited and updated, Cisco TMS creates a completely new route (the old route is not taken into
account when doing this). Even the smallest change to a conference could therefore create new dial-in numbers.
account when doing this). Even the smallest change to a conference could therefore create new dial-in numbers.
Cisco TMS will not take the initiative to reroute a conference. This means that for example:
■
If you change your number range on a TelePresence Server that has future conferences already routed by Cisco
TMS, all these future conferences on the TelePresence Server will assume the old dial plan. Run
TMS, all these future conferences on the TelePresence Server will assume the old dial plan. Run
■
If a conference is booked on SIP for a SIP-enabled system, and then SIP is disabled for that system, Cisco TMS will
understand that SIP is not enabled for this system any more but will not change the protocol for that call leg in the
conference booked before the change to the system was made.
understand that SIP is not enabled for this system any more but will not change the protocol for that call leg in the
conference booked before the change to the system was made.
Cisco TMS is able to route both IP and ISDN. Cisco TMS prioritizes IP if a system is capable of both. Over IP, H.323 is pri-
oritized over SIP.
oritized over SIP.
A conference can be split into several legs depending on how many participants there are, and each leg can use a dif-
ferent protocol.
ferent protocol.
Cisco Systems, Inc.
21