Cisco Cisco TelePresence Management Suite (TMS) Version 15 Maintenance Manual
Support for remote systems
Cisco TMS Administration Guide
Page 16 of 37
Adding a remote system to Cisco TMS
A system already added to Cisco TMS
The easiest way to add a remote system to Cisco TMS is to first have the system registered in Cisco
TMS before you bring it home. Before you unplug it, go to Edit Settings in the Settings tab for the
system and click Enforce Management Settings. If the system will be behind a firewall that is not
open or doesn’t have HTTP or HTTPS ports opened up, you also have to go to the Connection tab on
that endpoint and change System Connectivity to Behind Firewall. Cisco TMS will then set the
management address on that system to Cisco TMS external management address. When the system
is plugged in at home, the system will then send a boot event to Cisco TMS and from then on the
system will be available from Cisco TMS.
TMS before you bring it home. Before you unplug it, go to Edit Settings in the Settings tab for the
system and click Enforce Management Settings. If the system will be behind a firewall that is not
open or doesn’t have HTTP or HTTPS ports opened up, you also have to go to the Connection tab on
that endpoint and change System Connectivity to Behind Firewall. Cisco TMS will then set the
management address on that system to Cisco TMS external management address. When the system
is plugged in at home, the system will then send a boot event to Cisco TMS and from then on the
system will be available from Cisco TMS.
A system not added to Cisco TMS
If you want to use an endpoint that has not been added to Cisco TMS before it is plugged in at the
remote location, you will need to set the external management address of Cisco TMS on the endpoint.
This can be automatically done by the DHCP server (see section Configuring the DHCP server) or
manually on the endpoint. With F5.x and L4.1 this must be done using telnet, while F6.x and L4.2 (and
newer) have this in the endpoint’s menu:
remote location, you will need to set the external management address of Cisco TMS on the endpoint.
This can be automatically done by the DHCP server (see section Configuring the DHCP server) or
manually on the endpoint. With F5.x and L4.1 this must be done using telnet, while F6.x and L4.2 (and
newer) have this in the endpoint’s menu:
1. In Windows, go to Start > Run.
2. Type
telnet <ip-address of the endpoint>
(This can be displayed on the endpoint by
pressing the Up arrow and then the Left arrow.)
3. Type password if needed
4. Type
xConfiguration ExternalManager Address: “<dns name of the TMS
server>”
. If you are using a proxy, type the dns name of the proxy server instead.
5. This configuration is correct by default, but if it has changed, type ‘xConfiguration
ExternalManager Path: “tms/public/external/management/systemmanagementservice.asmx”’
6. Type
bye
When this has been set, the endpoint will send a register event to Cisco TMS, and when Cisco TMS
receives this and notices that the system is not already in Cisco TMS, it will add it to a list. One must
then add the system to Cisco TMS afterwards. However, if Automatic System Discovery Mode for
SoHo has been enabled, the system will be added in the default folder specified in the Administrative
Tools > Configuration > Network Settings.
receives this and notices that the system is not already in Cisco TMS, it will add it to a list. One must
then add the system to Cisco TMS afterwards. However, if Automatic System Discovery Mode for
SoHo has been enabled, the system will be added in the default folder specified in the Administrative
Tools > Configuration > Network Settings.
Setting an endpoint in public
If your system is in public, not behind a firewall or behind a firewall that has opened up the HTTP or
HTTPS ports, it is advised to change the system connectivity on the system to Reachable on Public
Internet. This way it will also be possible for Cisco TMS to set up calls where the endpoint is calling
out, and not only being called to.
HTTPS ports, it is advised to change the system connectivity on the system to Reachable on Public
Internet. This way it will also be possible for Cisco TMS to set up calls where the endpoint is calling
out, and not only being called to.
Booking
A booking in Cisco TMS including remote systems can be done like any other booking. However, as
Cisco TMS is not able to communicate directly to a remote system that is behind a firewall, it is not
possible for Cisco TMS to ask the endpoint to initiate a call. The endpoint must therefore be dialed
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.
Cisco TMS is not able to communicate directly to a remote system that is behind a firewall, it is not
possible for Cisco TMS to ask the endpoint to initiate a call. The endpoint must therefore be dialed
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.
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.