Cisco Cisco TelePresence Management Suite (TMS) Version 15 Installation Guide
Configuration topics
Cisco TelePresence Management Suite Installation and Getting Started Guide
Page 44 of 69
Note: The Cisco TMS Agent application does not use the fully qualified DNS hostname configured
here, although they may/could be the same in a single Cisco TMS environment (recommended). The
Cisco TMS Agent uses the actual local hostname of the Cisco TMS server and this must match the
DNS A record for the Cisco TMS Agent. In a Cisco TMS redundant setup, the fully qualified DNS
hostname configured here must be unique and resolvable to reflect the Cisco TMS redundancy; that
is, resolvable to the network load balancer. However, DNS records for each particular redundant
Cisco TMS (local hostname) will also need to be created so that the Cisco TMS Agent can resolve
and thereby replicate between the TMSs appropriately.
here, although they may/could be the same in a single Cisco TMS environment (recommended). The
Cisco TMS Agent uses the actual local hostname of the Cisco TMS server and this must match the
DNS A record for the Cisco TMS Agent. In a Cisco TMS redundant setup, the fully qualified DNS
hostname configured here must be unique and resolvable to reflect the Cisco TMS redundancy; that
is, resolvable to the network load balancer. However, DNS records for each particular redundant
Cisco TMS (local hostname) will also need to be created so that the Cisco TMS Agent can resolve
and thereby replicate between the TMSs appropriately.
TMS Server Address (Fully Qualified Host Name or IPv4 Address)
– Public or Behind the
Firewall respectively - This must be the fully qualified DNS hostname used to access your
Cisco TMS server from an outside network if that is different from the local hostname. This setting
must be configured to use features such as SOHO/Behind Firewall support. If the server has no
hostname that is usable, enter the IP address that systems would use to reach Cisco TMS.
Cisco TMS server from an outside network if that is different from the local hostname. This setting
must be configured to use features such as SOHO/Behind Firewall support. If the server has no
hostname that is usable, enter the IP address that systems would use to reach Cisco TMS.
Automatic Software Update
– This functionality allows Cisco TMS to automatically check for
new software available for your systems over a secure link, and to notify you of your Service
Contract status for your Cisco TelePresence Systems. No personal information is sent during this
communication except the system identification information such as serial numbers and hardware
identifiers. If you do not wish to have Cisco TMS check for software, you can disable this feature.
If your network requires a web proxy to reach the internet, configure its properties here.
Contract status for your Cisco TelePresence Systems. No personal information is sent during this
communication except the system identification information such as serial numbers and hardware
identifiers. If you do not wish to have Cisco TMS check for software, you can disable this feature.
If your network requires a web proxy to reach the internet, configure its properties here.
Secure-Only Device Communication
– This setting is disabled by default and only be enabled
Cisco TMS installation media for more information.
Significant Administrative Tools > E-Mail Settings were configured during the Cisco TMS
installation. However, if your mail server requires SMTP Auth to be able to send email, configure an
appropriate username and password here. The settings are tested when you click Save to ensure that
they are valid.
installation. However, if your mail server requires SMTP Auth to be able to send email, configure an
appropriate username and password here. The settings are tested when you click Save to ensure that
they are valid.
Significant Administrative Tools > Conference Settings settings control most of the Cisco TMS
behavior for scheduled calls and for monitoring of active calls. Significant settings are:
behavior for scheduled calls and for monitoring of active calls. Significant settings are:
Default Bandwidth
– The default bandwidth suggested for H.323 and SIP calls in Cisco TMS
Scheduling.
Default ISDN Bandwidth
– The default bandwidth suggested for ISDN calls in Cisco TMS
Scheduling
Set Conferences as Secure by Default
– Cisco TMS can work with systems that support
encryption and those that do not. This setting controls the default behavior for Scheduled
Conferences. „If Possible‟ is the default setting and enables encryption when all systems in a call
support it.
Conferences. „If Possible‟ is the default setting and enables encryption when all systems in a call
support it.
WebEx integration
For WebEx booking to work, the booking user must have a WebEx User & Password defined in their
Cisco TMS profile. This is done so the correct user 'owns' the meeting in WebEx and can log in and
operate the WebEx call.
Cisco TMS profile. This is done so the correct user 'owns' the meeting in WebEx and can log in and
operate the WebEx call.
Early iterations of WebEx used a shared account, which while made booking available to everyone, it
was less functional because users did not have the correct permissions on the created WebEx
meetings.
was less functional because users did not have the correct permissions on the created WebEx
meetings.