Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
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 or legacy systems such as the TANDBERG Gatekeeper. Cisco TMS
just checks whether the gatekeeper IP address value is the same for both systems.
can even be unsupported third party or legacy systems such as the TANDBERG Gatekeeper. 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
.)
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
this MCU. This means you can produce an ISDN dial-in number for a booked conference instead of using a
TCS4 dial in.
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
this MCU. This means you can produce an ISDN dial-in number for a booked conference instead of using a
TCS4 dial in.
If you do not set up DID mapping, you can set a dial-in ISDN number for the gateway in the IP zone. Cisco
TMS then creates a dial in using the ISDN number of the gateway plus a * then the alias of the meeting you
are going to join.
TMS then creates a dial in using the ISDN number of the gateway plus a * then the alias of the meeting you
are going to join.
Cisco Unified Communications Manager
If a system is provisioned by 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 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 Unified CM and vice versa.
assumes that it will work and that the Cisco VCS is able to route calls to the Unified CM and vice versa.
n
will always append the top level domain to calls going through the Unified CM - make sure the Cisco VCS
accepts this kind of dial plan/numbering scheme.
accepts this kind of dial plan/numbering scheme.
Cisco TelePresence Management Suite Administrator Guide (14.5)
Page 44 of 340
Routing
What infrastructure does Cisco TMS use for routing?