Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Support for remote systems/SoHo systems
Cisco TMS Administration Guide
Page 19 of 39
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 int ernal
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 soft ware package.
This URL is defined in Admini strative Tool s > Network > General Network Settings. It is
recommended that the directory is left to the default (tms/public/data/soft ware) as this is where Cisco
TMS populates its list of packages from (System s > 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.
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 soft ware package.
This URL is defined in Admini strative Tool s > Network > General Network Settings. It is
recommended that the directory is left to the default (tms/public/data/soft ware) as this is where Cisco
TMS populates its list of packages from (System s > 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.
Statistics and monitoring
The statistics and monitoring of the remote systems will be made up the same way as systems that
are on the LA N, 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 Refre sh in Cisco TMS) or when
doing changes in Cisco TMS.
are on the LA N, 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 Refre sh in Cisco TMS) or when
doing changes in Cisco TMS.
Ad hoc calls will not be shown for systems behind a firewall as the TMS LiveService 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.
•
/tms/public/external/management/systemmanagementservic e.asmx
•
/tms/public/feedback/code.aspx
•
/tms/public/external/phonebook/phonebookservice.asmx
•
/tms/public/feedback/postdocument.aspx
Have two Cisco TMS
servers, one on the
inside and one in DMZ
talking to the same
database
servers, one on the
inside and one in DMZ
talking to the same
database
This will allow you to add and manage the internal and external systems
seamlessly, but requires some extra configuration of firewalls and the
external Cisco TMS server.
seamlessly, but requires some extra configuration of firewalls and the
external Cisco TMS server.
The Cisco TMS server in the DMZ should only be accessible on port 80 from
the Int ernet, and can als o be limited to only respond to connections, but not
open any new connections. The Cisco TMS in the DMZ must be able to talk
to the SQL server on the inside of the network, but this can be limited to one
port only. It is recommended to use a limited user with only read/ write
permissions to the tmsng database for this (doing upgrades of the Cisco
the Int ernet, and can als o be limited to only respond to connections, but not
open any new connections. The Cisco TMS in the DMZ must be able to talk
to the SQL server on the inside of the network, but this can be limited to one
port only. It is recommended to use a limited user with only read/ write
permissions to the tmsng database for this (doing upgrades of the Cisco