Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
this MCU. This means you can produce an ISDN dial-in number for a booked conference instead of using a
TCS4 dial in:
TCS4 dial in:
The alternative if you do not set up DID mapping is to set a dial-in ISDN number for the gateway in the IP
zone and Cisco TMS creates a dial in using the ISDN number of the GW plus a * then the alias of the meeting
you are going to join.
zone and Cisco TMS creates a dial in using the ISDN number of the GW plus a * then the alias of the meeting
you are going to join.
Gatekeeper
When Cisco TMS wants to create a route between two or more systems, it looks at whether systems are
registered to the same or different gatekeepers.
registered to the same or different gatekeepers.
The systems are registered to the same gatekeeper
Cisco TMS knows they can dial each other - the gatekeepers do not have to be registered in Cisco TMS and
can even be unsupported third party gatekeepers. Cisco TMS just checks whether the gatekeeper IP
address value is the same for both systems.
can even be unsupported third party gatekeepers. Cisco TMS just checks whether the gatekeeper IP
address value is the same for both systems.
The systems are registered to different gatekeepers
Cisco TMS must know whether there is a relationship between the gatekeepers to understand whether the
two systems can dial each other.
two systems can dial each other.
If the gatekeepers are registered in Cisco TMS, it will look at neighbor zones or cluster relationships on the
gatekeepers to see if they can dial each other.
gatekeepers to see if they can dial each other.
If the gatekeepers are not in Cisco TMS, it assumes there is no relationship between them and will use IP
dialing.
dialing.
If you configure an IP zone with a Domain URL, then Cisco TMS understands this can be used for systems
to dial one another. (See
to dial one another. (See
.)
Cisco Unified Communications Manager
If a system is provisioned by Cisco Unified CM and there is a trunk to a Cisco VCS, Cisco TMS:
n
will never use H.323 for the system even though it might support it.
n
will never use IP dialing for the system.
n
cannot verify that the trunk between the Cisco Unified CM and the Cisco VCS is set up correctly, Cisco
TMS assumes that it will work and that the Cisco VCS is able to route calls to the Cisco Unified CM and
vice versa.
TMS assumes that it will work and that the Cisco VCS is able to route calls to the Cisco Unified CM and
vice versa.
n
does not support MCUs or Cisco TelePresence Servers SIP-trunked to the Cisco Unified CM. These must
be registered to the Cisco VCS.
be registered to the Cisco VCS.
n
supports only one Cisco Unified CM top level domain.
n
will always append the top level domain to calls going through the Cisco Unified CM - make sure the Cisco
VCS accepts this kind of dial plan/numbering scheme (unless you turn off native interop call routing).
VCS accepts this kind of dial plan/numbering scheme (unless you turn off native interop call routing).
n
only supports one Cisco Unified CM cluster (one top level domain).
If you want to call between earlier versions of Cisco TelePresence systems and systems running TE and TC
software you need a Cisco TelePresence Server to bridge the call. If you do not have a TelePresence Server,
select Yes in:
software you need a Cisco TelePresence Server to bridge the call. If you do not have a TelePresence Server,
select Yes in:
Cisco TMS Administrator Guide (14.1)
Page 37 of 320
Routing
What infrastructure does Cisco TMS use for routing?