Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Support for remote systems/SoHo systems
Cisco TMS Administrator Guide
Page 18 of 37
into. If two or more systems that are behind a firewall would like to call each other, then an internal
system with multisite must be included in the call.
system with multisite must be included in the call.
Phonebooks
The phonebook will work in the same way as if the system was located on a LAN. When the endpoint
is requesting the phonebook, it will send the request to the Cisco TMS server where Cisco TMS
creates the .xml file and sends it back to the endpoint as the response.
is requesting the phonebook, it will send the request to the Cisco TMS server where Cisco TMS
creates the .xml file and sends it back to the endpoint as the response.
Calendar
The calendar will be sent via piggybacking on the boot, registration or heartbeat message from the
endpoint.
endpoint.
Software upgrade
Software upgrade on remote systems is set up in the same way as software upgrade on internal
systems. However, the mechanism used to upgrade the system is different. When you have
scheduled the upgrade, Cisco TMS will say that the upgrade went successfully. What has happened is
that Cisco TMS has put the upgrade on hold until it gets a boot event from the system. When Cisco
TMS gets this boot event, it will see that an upgrade has been scheduled for that system. On the reply
to the boot event, Cisco TMS will send the endpoint a URL where it can get the software package.
This URL is defined in
systems. However, the mechanism used to upgrade the system is different. When you have
scheduled the upgrade, Cisco TMS will say that the upgrade went successfully. What has happened is
that Cisco TMS has put the upgrade on hold until it gets a boot event from the system. When Cisco
TMS gets this boot event, it will see that an upgrade has been scheduled for that system. On the reply
to the boot event, Cisco TMS will send the endpoint a URL where it can get the software package.
This URL is defined in
Administrative Tools > Network > General Network Settings
. It is
recommended that the directory is left to the default (tms/public/data/software) as this is where Cisco
TMS populates its list of packages from (
TMS populates its list of packages from (
Systems > System Upgrade > Software Manager
). In other
words, if you provide a different URL, you might end up scheduling an upgrade with a package found
in the list that is not found in the URL specified.
in the list that is not found in the URL specified.
Statistics and monitoring
The statistics and monitoring of the remote systems will be made up the same way as systems that
are on the LAN, by sending event traps to Cisco TMS. As for retrieving status and detailed call
information (‘status.xml’ and ‘history.xml’), these are sent every 15 minutes. The configuration of the
system (‘configuration.xml’) will be sent on demand (clicking Force Refresh in Cisco TMS) or when
doing changes in Cisco TMS.
are on the LAN, by sending event traps to Cisco TMS. As for retrieving status and detailed call
information (‘status.xml’ and ‘history.xml’), these are sent every 15 minutes. The configuration of the
system (‘configuration.xml’) will be sent on demand (clicking Force Refresh in Cisco TMS) or when
doing changes in Cisco TMS.
Ad hoc calls will not be shown for systems behind a firewall as the TMSLiveService service is not able
to contact the system to get information about the call.
to contact the system to get information about the call.
Cisco TMS configuration
To allow for the remote systems to communicate with the Cisco TMS server, Cisco TMS needs to be
reachable from the remote system. There are several ways that this can be done:
reachable from the remote system. There are several ways that this can be done:
Alternative:
Description
Put the Cisco TMS in
public
public
This option provides less security, and makes the Cisco TMS vulnerable for
attacks directly over the Internet.
attacks directly over the Internet.
Put the Cisco TMS in
DMZ
DMZ
This option provides a bit more security. Port 80 (HTTP) needs to be open in
the firewall to allow for incoming traffic.
the firewall to allow for incoming traffic.
Use a proxy
This option provides the best security without having to have two separate
Cisco TMS servers, and is set up by having the proxy forward to the Cisco
TMS server requests that are made to the management address path of the
Cisco TMS server.
Cisco TMS servers, and is set up by having the proxy forward to the Cisco
TMS server requests that are made to the management address path of the
Cisco TMS server.