TANDBERG TELEPRESENCE MANAGEMENT SUITE SECURE SERVER - CONFIGURATION GUIDE... Instruction Manual

Cisco TMS Administration Guide Page 1 of 37
Cisco TelePresence
Management Suite
Administration Guide
D13741.12
December 2010

Cisco TMS Administration Guide Page 2 of 37
Table of Contents
Introduction......................................................................................................................... 5
Zones ................................................................................................................................... 6
ISDN zones ............................................................................................................................................. 6
Area code rules ................................................................................................................................ 7
IP zones................................................................................................................................................... 8
Gateway resource pool .................................................................................................................... 8
Adding systems..................................................................................................................10
Automatic system discovery.................................................................................................................. 10
Add systems.......................................................................................................................................... 10
Feedback from Cisco TMS when adding systems, rooms and equipment.................................... 11
Adding a Cisco TelePresence Content Server...............................................................................11
How pre-registration works.................................................................................................................... 12
Configuring the DHCP server.........................................................................................................12
Persistent settings ................................................................................................................................. 12
Swap a system in Cisco TMS................................................................................................................13
Replace system function................................................................................................................ 13
System tracked by IP address........................................................................................................ 13
System tracked by Host Name....................................................................................................... 13
System tracked by MAC address................................................................................................... 14
Support for remote systems..............................................................................................15
How the communication works.............................................................................................................. 15
Reachable on public Internet..........................................................................................................15
Behind firewall................................................................................................................................ 15
Plugging in at remote location........................................................................................................15
Adding a remote system to Cisco TMS.................................................................................................16
A system already added to Cisco TMS.......................................................................................... 16
A system not added to Cisco TMS................................................................................................. 16
Setting an endpoint in public..........................................................................................................16
Booking.................................................................................................................................................. 16
Phonebooks........................................................................................................................................... 16
Software upgrade .................................................................................................................................. 17
Statistics and monitoring ....................................................................................................................... 17
Cisco TMS configuration ....................................................................................................................... 17
User permissions...............................................................................................................19
User Administration ............................................................................................................................... 19
User Information and preferences..................................................................................................19
Limiting access to Cisco TMS/Locking out a set of users.....................................................................20
Groups................................................................................................................................................... 20
Access to different parts of Cisco TMS..........................................................................................21
Users ..................................................................................................................................................... 21
Default Groups ...................................................................................................................................... 22
Default System Access.......................................................................................................................... 22

Introduction
Cisco TMS Administration Guide Page 3 of 37
Phone Books ......................................................................................................................23
Local Directory....................................................................................................................................... 23
Global Directory..................................................................................................................................... 23
Corporate Directory ............................................................................................................................... 23
Setting phone books on systems .......................................................................................................... 23
Cisco TMS features............................................................................................................25
Operator conferences............................................................................................................................ 25
Operator conference features: ....................................................................................................... 25
How to set up an operator conference........................................................................................... 25
Provisioning directory............................................................................................................................ 25
Troubleshooting the Cisco TMS components..................................................................27
Phonebook (Corporate Directory) errors............................................................................................... 27
TMSDatabaseScannerService.............................................................................................................. 27
Symptoms....................................................................................................................................... 28
How to fix........................................................................................................................................ 28
TMSLiveService .................................................................................................................................... 28
Symptoms....................................................................................................................................... 28
How to fix........................................................................................................................................ 28
TMSPLCMDirectoryService................................................................................................................... 29
Symptoms....................................................................................................................................... 29
How to fix........................................................................................................................................ 29
TMSSchedulerService........................................................................................................................... 29
Symptoms....................................................................................................................................... 29
How to fix........................................................................................................................................ 29
TMSSnmpService (formerly TMSWatchdogServiceStarter.exe) .......................................................... 29
Symptoms....................................................................................................................................... 30
How to fix........................................................................................................................................ 30
TMSServerDiagnosticsService.............................................................................................................. 30
Symptoms....................................................................................................................................... 30
How to fix........................................................................................................................................ 30
Cisco TMS Database Management Service (optional).........................................................................31
Symptoms....................................................................................................................................... 31
How to fix........................................................................................................................................ 31
TMSAgentService.................................................................................................................................. 31
Symptoms....................................................................................................................................... 31
How to fix........................................................................................................................................ 31
The Web server..................................................................................................................................... 31
Symptoms....................................................................................................................................... 32
How to fix........................................................................................................................................ 33
Java Applet – Monitoring.......................................................................................................................33
What it does.................................................................................................................................... 33
Symptoms....................................................................................................................................... 33
How to fix........................................................................................................................................ 33
The database......................................................................................................................................... 34
Symptoms....................................................................................................................................... 34
How to fix........................................................................................................................................ 34
Related documents............................................................................................................36

Introduction
Cisco TMS Administration Guide Page 4 of 37
Disclaimers and notices ....................................................................................................37

Introduction
Cisco TMS Administration Guide Page 5 of 37
Introduction
The Cisco TelePresence Management Suite (Cisco TMS) is a portal for managing and monitoring your
video conferencing system from a single structured overview. Cisco TMS provides centralized control
for on-site and remote video systems, and a deployment and scheduling system for your entire video
network.
Cisco TMS can be downloaded from Cisco.com.
Cisco TMS is a powerful tool for maintaining, operating, and increasing the value of your conferencing
network. Cisco TMS adds intelligence, diagnostics, and functionality that enhance your video network
components and the return on your investment.
Cisco TMS automates system configuration for a basic H.323 network, operating ‘right out of the box’.
You can tune Cisco TMS default behavior to suit your organization needs, set up user permissions,
and configure your network model so that all of Cisco TMS call handling functionalities are available.
This document provides information for fresh installs, upgrading an existing version, or configuring the
Cisco TMS version that comes preinstalled on a Cisco TelePresence Management Server. There is
also a guide for uninstalling Cisco TMS.
Along with installation/upgrade processes, you will find guidelines on software and hardware
requirements, integrating Cisco TMS with other applications, and version specific upgrade information.
Further information on Cisco TMS functionality is available online. Cisco also maintains a Cisco TMS
knowledgebase.
Note: For the Cisco TMS user guide, see the online help available via the question mark icon (?) on
the Cisco TMS client.
A list of relevant documents referred to in this guide can be found in the References and related
documents section.

Zones
Cisco TMS Administration Guide Page 6 of 37
Zones
Zones enable Cisco TMS to use the correct international dialing codes when using ISDN between
countries (area codes within the same country), selecting which systems should use IP and which
should use ISDN, and insert the correct prefixes for IP systems when using an ISDN gateway.
Systems in the same IP zone will always connect on IP as default when they are booked via Cisco
TMS. If you always want to use ISDN between systems in a location, they should therefore not be part
of an IP zone. Also, systems that will never connect on ISDN (except through a gateway) should not
be part of an ISDN zone.
ISDN zones
To set up an ISDN zone, go to Administrative Tools > Locations > ISDN Zones, click New and fill in
the following fields:
ISDN Zone Name
Specify the name of the ISDN zone.
Country/Region
Choose the country this zone is situated in. This will let
Cisco TMS choose the correct country code and correct
international dialing prefixes.
Area Code
Specify the area code this zone is situated in. This will let
Cisco TMS choose the correct area code rules
To access an outsid
e line for
local calls, dial Insert the prefix needed to gain an outside line in this ISDN
zone
To access an outside line for
long distance calls, dial Insert the prefix needed to gain an outside line for long
distance calls in this ISDN zone.
Note: If you use the same prefix to gain an outside line for
both local and long distance calls you should put the same
prefix here as you put in the previous field.
Number of digits to use for
internal ISDN calls This specifies the number of digits used for internal dialing
within this zone. The leading digits will be stripped from the
number when dialing between systems in this ISDN zone.
Note: If Cisco TMS is generating the wrong numbers to dial when dialing local, domestic or
international calls, you should have a look at the ISDN zone settings and the phone number set on
the system.
Example:
A Swedish phone number in Stockholm would have a number layout like this:
Country code (+46); Area code (08); local number (12345678)
 If dialing this number from within Stockholm they would only dial the local number: 12345678
 If dialing from Gothenburg (within the country, but outside the area code) they would dial: 08
12345678
 If dialing from outside Sweden they would dial: [phone]
As you see the 0 in front of 8 (in the area code) would have to be removed when dialing this number
from outside the country. This is therefore not looked upon as part of the area code, but rather a prefix
to dial between area codes.
The systems should only be configured with the local ISDN number: 12345678, but with the correct
area and country code in the ISDN Zone. If the system was wrongly configured with the local number
and the area code, Cisco TMS would wrongly configure the following as the international number for
the system: [phone]

Zones
Cisco TMS Administration Guide Page 7 of 37
In the ISDN Zone the area code should be stored as just 8, since Cisco TMS will add a 0 in front of it
when dialing between Swedish area codes, and add +46 when dialing from outside Sweden.
There are some exceptions to these rules, but Cisco TMS is aware of these exceptions.
 Some countries like Norway do not use area codes; the area code field in the ISDN zones in
these countries should therefore be left empty. An example of a valid number is [phone].
 Some other countries like Italy include the leading zero in the area code even when being dialed
into from outside the country. This means that the area codes in the Italian ISDN zones should
include the leading zero. An example of a valid number is [phone].
 Other countries again such as Switzerland include the area code with the leading zero when
dialing within an area code and when dialing within the country, but remove the leading zero when
being dialed into from outside the country. Cisco TMS knows this, so the area code for ISDN
zones in Switzerland should only include the area code without the leading zero. For example:
[phone] and 033 1234567.
Area code rules
Area code rules are typically used in the US to set up 10-digit dialing and area code overlays. Area
code rules determine how ISDN numbers are dialed from one area code (the area code set for the
location) to other area codes.
To add or edit an area code rule for a location, click Area Code Rules inside the ISDN zone. After
clicking the link, a page with an overview of all area code rules for the ISDN zone is displayed.
New rules can be added to the location from this page by clicking New Rule.
You can edit old rules for the location by clicking the Edit links to the right of every rule.
To delete a rule, select it and click Delete.
Note: In a US phone number, for example [phone], the area code consists of the digits in
brackets (123), and the prefix consists of the digits 456 (in this example).
Create a new dialing code for the selected location by clicking New Rule.
When adding a new rule for a location, fill in the fields as described below.
When dialing from this area code to the
following area code (Field 1)
This field, combined with the prefix field explained
below, decides the area code that this rule applies to. It
may be set to be the same area code used for the
location.
With the following prefixes (Field 2)
The rule will only apply to the calls made to the area
code in Field 1, with the prefixes listed here. If this field
is left empty, the rule will apply for all calls made to the
area code in Field 1.
Include Area Code
If checked, the area code in Field 1 will be included in
the call. If unchecked, the area code will not be included
in the call. For the US, select this check box to enable
10-digit dialing.
Before dialing, also dial
If the rule applies, as stated in Field 1 and Field 2, the
digit(s) in this field will be dialed first when making a call.
In most cases this field will be empty.
Click Save when you are done defining your new area code for this ISDN zone.
Note: When an Area Code rule is used, prefixes from the ISDN zone are still used, but domestic
dialing behaviors (such as inserting a 1) are ignored by Cisco TMS.

Zones
Cisco TMS Administration Guide Page 8 of 37
IP zones
To set up an IP Zone:
1. Go to Administrative Tools > Locations > IP Zones.
2. Click New.
3. Fill in the fields described below.
Field Description
IP Zone Name
Specify the name of the IP zone
Gateway resource pool
ISDN Zone
By moving IP zones between the two lists at the bottom of an IP zone, you can specify which IP zones
should be dialed using IP, and which IP zones should be dialed using ISDN.
When setting up a conference with participants in different IP zones, Cisco TMS will try to include a
Cisco TelePresence MCU from the IP zone where the majority of the participants are situated.
In the Gateway Resource Pool settings you specify which prefixes to dial in order to use a gateway.
The ISDN Zone dropdown allows you to specify which ISDN Zone’s dialing rules should apply to the
gateway you want to use. The reason you specify the prefix rather than the gateway directly, is that
this allows for more flexibility in Cisco TMS. It means that you can use load-balanced gateways, and
even gateways not supported by Cisco TMS.
Note: This setting must be specified in order for the Gateway Resource Pool to work.
Field Description
URI Domain Name:
Add which domain name Cisco TMS should use for routing H323 calls
to this IP-zone when doing URI dialing.
Note: Cisco TMS will always use URI dialing between two locations
where this setting is filled in, thereby ignoring the IP/ISDN
preferences defined at the bottom of this page.
Gateway Auto Prefix:
Specify the prefix to use to get an outside ISDN line through the
gateway for video calls.
Gateway Telephone Prefix:
Specify the prefix to use to get an outside ISDN line through the
gateway for telephone calls.
Gateway 3G Prefix:
Specify the prefix to use to get an outside 3G line through the 3G
gateway for 3G calls.
Dial
-
in ISDN Number:
Specify the TSC4 number that will be used for dialing into endpoints
through a gateway. Cisco TMS will automatically generate the entire
number for a call containing the gateway’s TSC4 number followed by
the star and the endpoint’s E164 alias.
Dial
-
in ISDN Number for
3G: Specify the TSC4 number that will be used for dialing into endpoints or
Cisco TelePresence MCU through a 3G gateway. Cisco TMS will
automatically generate the entire number for a call containing the
gateway’s TSC4 number followed by the star and the endpoint’s E164
alias.
Allow IP
-
ISDN
-
IP:
Check this option to allow Cisco TMS to schedule calls from an IP only
endpoint out through an IP-ISDN gateway to an IP only endpoint in via
an ISDN-IP gateway. The set-up time for this type of calls can be close

Zones
Cisco TMS Administration Guide Page 9 of 37
Field Description
to a minute.
Prefer IP calls to specific
IP zones: Systems in the same IP zone will always prefer to dial each other on
IP. This will be the preferred call option when booking via Cisco TMS
booking and the only option when using a different booking interface
like Outlook, Lotus Notes, Microsoft Office Communicator, Lotus
Sametime or Cisco Scheduler. The systems in the same IP zone will
be dialed on E164 alias if all systems in the conference are registered
to one gatekeeper or different neighboring gatekeepers. Participants
that are not reachable through a gatekeeper will be dialed to (or from)
with IP-addresses.

Adding systems
Cisco TMS Administration Guide Page 10 of 37
Adding systems
Systems in Cisco TMS include Endpoints, Gateways, Gatekeepers, Cisco TelePresence MCU,
Equipment and Rooms. Every system can be represented in multiple folders, but these
representations will all have the same entry in the database – which means that changes done to the
system will be reflected in all of its representations.
Automatic system discovery
From Cisco TMS 11.5 a new feature called Automatic system discovery was added. This feature
can be turned on during installation or after installation by going to Administrative Tools >
Configuration > Network Settings. When this feature is enabled, Cisco TMS will scan the network
for systems. If a system not yet known to Cisco TMS responds, this system will automatically be
added to a default folder and given a default template. This template will include an IP Zone and a
Cisco TMS Phonebook containing all the endpoints in Cisco TMS. The folder and template can be
changed under Administrative Tools > Configuration > Network Settings.
Add systems
To add systems, go to Systems > Navigator > select folder to add system to > click Add System.
This page contains four different tabs where you can add systems to the selected folder in Cisco TMS.
Each of them allows different ways of adding systems and rooms/equipment:
Add Systems tab
On this page you can either enter a start IP address and an end IP address for a range of systems to
be added, or you can enter a comma-separated list of IP addresses and host addresses for those
systems you want to add to the Cisco TMS. The following example will add two systems, one by DNS
name and one by IP address, and scan ten systems in a range: “user.tms.int, 10.0.0.1, 10.1.1.0 -
10.1.1.10”
This page is also where you specify the correct locations for the systems and the time zone.
In the Advanced Setting pane you can:
 Enter Username, Password and/or an Admin Password if the systems require it in order to be
added.
 Select a template to be set as persistent settings on the systems.
 Set Discovery Options. For example which SNMP names to use when searching for systems
and if you want to search for non-SNMP systems and whether or not to add discovered systems
although they are not supported by Cisco TMS (for example PC’s and network infrastructure
devices). The list of SNMP community names is pulled from Administrative Tools >
Configuration > Network Settings > SNMP Community Names. If you know the community
names of the system you want to add, you may edit this field to speed up the adding process. Any
changes here will NOT affect the settings under Administrative Tools.
 The Usage Type field specifies the usage of the system that is added. The options are: Meeting
Room, Personal Home System, Personal Office System or a Roll About system.
From List tab
On this page you can add systems that have already been added to Cisco TMS but are not already in
the current folder or have been automatically discovered by the Cisco TMS Network Scanner.
 To select the systems you want to add to the folder, select the check box to the left of the
systems.
 Specify the locations and the time zone you want the systems to have in the Enter Location
Settings pane.
 For systems that require authentication data, this is entered in the Advanced pane.

Adding systems
Cisco TMS Administration Guide Page 11 of 37
Pre Register Systems tab
If you are planning to deploy a large number of endpoints, pre-registering them allows Cisco TMS to
configure the systems the first time they come online. When you pre-register, you must supply a name
for the system and an identifier. You must first select what to use as primary identifier; MAC address,
IP or Serial Number for the systems.
Note: Currently only the Cisco TelePresence System MXP series and Polycom HDX support using
serial number as the identifier. Cisco recommends using MAC address as the unique identifier for
systems.
 If you want a list of settings to be applied to the system when it comes online, you can select a
pre-created template from the list in the Set templates pane. This template can be modified at
any time using the template pages. A persistent template for the system can also be
preconfigured here, together with the option of setting persistent E164 Alias, H323Id, SIP URI and
the endpoint name. The templates and persistent settings require that the system supports
templates in Cisco TMS.
 Specify the locations and the time zone you want the systems to have in the Enter Location
Settings pane.
To learn more, see How pre-registration works.
Add Rooms/Equipment tab
Here you choose whether you want to enter a room or a type of equipment.
Start by entering the name of the room or equipment you want to add to the Cisco TMS.
If you select to add a room, you can specify more settings in the advanced area. In the advanced area
you may enter information about IP, ISDN, Gatekeeper, SIP and location settings.
Feedback from Cisco TMS when adding systems, rooms and equipment
When adding systems and rooms/equipment, Cisco TMS will analyze the systems configurations
using the ticketing service to ensure that when a system is added its settings are verified.
If Cisco TMS finds any faulty configurations, it will present the system in the table with the header
saying “NOTE: Systems Discovered with Incorrect Settings, Not Yet Added to Folder:” with a
description in the table row saying what is wrong.
You may change/correct the settings by clicking Edit in the table row where the system is presented.
Change the settings for the system in the pop-up window. Have the user guides for the systems
available.
If there are no incorrect system settings, the system will be added to the folder and will be shown in
the table saying “Systems Discovered and Successfully Added to Folder:”
If the system is already added to the folder, you will get a message saying that it already is in the
folder. The system will be added to the table saying “Systems Discovered and Successfully Added
to Folder:”
If the system couldn’t be added because the SNMP Community Name is not added to the list in Cisco
TMS, or Cisco TMS couldn’t get in contact with the system or the system is of a type that TMS does
not support, it will be added to the table saying “NOTE: Systems That Could Not Be Added:”.
Adding a Cisco TelePresence Content Server
TMS 11 and versions onwards support adding the Cisco TelePresence Content Server for booking
and management purposes.
 To add the Content Server to Cisco TMS follow the procedures in the Add Systems tab
description.
 Select the Discover Non-SNMP Systems. WARNING: Will significantly increase time
required for discovery check box in the Advanced Settings pane of the tab.
Note: You need to add the Content Server’ API user and password when adding the system to Cisco
TMS.

Adding systems
Cisco TMS Administration Guide Page 12 of 37
How pre-registration works
When pre-registering a system, you can select whether you want the system to be identified on MAC
Address, IP/Hostname or Serial Number.
Note that only the Cisco TelePresence System MXP series and Polycom HDX endpoints can pre-
register based on serial number. Also keep in mind that only systems supporting SNMP can be pre-
registered by serial number and MAC-address if they are using static IP addresses. Cisco
TelePresence System MXP endpoints are using HTTP traps rather than SNMP traps to communicate
with the Cisco TMS server for most information. They are therefore dependent on having their
External Manager’s IP address configured. This is done automatically when the endpoint contacts the
DHCP server to retrieve an IP address, but only if the option 242 on the DHCP server is configured to
point to the Cisco TMS server.
Configuring the DHCP server
If you are using a Windows 2000/2003 DHCP server, add the following settings in the
DHCP Manager
You can create the 242 option by redefining an existing global option. To do this, highlight the global
option in the “Unused” list and click Add in the DHCP manager. Once you have defined a vendor-
specific option, you can select it for use by the vendor class by moving the option to the “Configured”
list, and defining its value which should be the IP or the DNS name of the Cisco TMS server.
If you are using ISC’s DHCP-server, put the following statements in dhcpd.conf.
1. Define option 242:
option local-tms-ip code 242 = ip-address;
2. Define the value in the subnet of pool section:
option local-tms-ip < IP address>;
If the systems are not using DHCP, they need to be able to respond to the SNMP broadcast
messages that Cisco TMS will send out on set intervals. This interval is configurable in
Administrative Tools > Configuration > Network Settings > TMS Services >SNMP Broadcast
Interval (in minutes).
Note: The Cisco 150 MXP with L1.1 and L1.2 is configured to request the DHCP for option 173. It is
therefore advised to either upgrade the endpoints to newer software, or to configure both the option
242 and 173 on the DHCP server until the endpoints are upgraded.
Persistent settings
Persistent settings allow the administrator to enforce settings on systems throughout the network.
These persistent settings can be specified during pre-registration or after the system has been added
to Cisco TMS (via the Persistent settings tab in Navigator).
The persistent settings will be set on the endpoint every time Cisco TMS receives a boot event from
the endpoint; either via SNMP or HTTP. The Persistent setting template is also set on the system at
the same time every day. This time is based on the first time the template was set on the system and
is configurable when editing the template in the Systems > Provisioning > Configuration
Templates page.
To view a log of the daily updates go to Systems > Provisioning Activity Status. You will see that
there are 2 types of entries; the first will be when the template has been set on the system and this will
have no recurrence set. As the second entry you will see the template again but the recurrence will be
set to every day. If you click on this description, you will see a log of all transactions for this template.
There are four persistent settings, and three of them allow you to set a persistent System Name,
H323 Id, E164 Alias and SIP URI. The last setting gives you the option to pick a predefined template
that will be set on the endpoint after every system boot. The template can typically include settings like
Auto answer on, Microphone off and Volume 7.

Adding systems
Cisco TMS Administration Guide Page 13 of 37
Swap a system in Cisco TMS
Systems get an id (Cisco TMS System Id) when they are first added to Cisco TMS. This id is used as
the reference for the systems in booking, reporting, event, permissions etc. It is therefore important to
retain the id, even if a system gets swapped (because of theft, upgrade, hardware failure etc). A
system should therefore never be purged from Cisco TMS. It may be deleted from a folder since the
data for the system will still be in the database, but it should not be purged unless you are 100%
confident that a new system should take over this system’s roles.
If a system in Cisco TMS is out of order, or awaiting a swap, it can be set to Not Allow Bookings. This
is done in the Connection tab in Systems > Navigator. By doing this you can avoid anyone booking
the system while it is unavailable.
Replace system function
From Cisco TMS 11.5 a feature called ‘Replace system’ was introduced. This feature makes it much
easier to replace systems in Cisco TMS. Cisco recommends using this feature when replacing
systems in Cisco TMS.
To replace a system:
1. Go to Systems > Navigator > select the system you wish to replace
2. Click the Connection tab.
3. Click Replace Systems. Here you choose whether to change the system’s network address to an
IP or DNS address of a system on the network, or choosing an existing system in Cisco TMS by
clicking Select system….
4. Click Next… You will then be shown a summary page where you choose whether you would like
to keep the system name, keep call configuration, apply last configuration backup and keep all
logs of the system. You can also choose to purge the system that you are replacing from Cisco
TMS.
5. Click OK and the switch will be completed.
System tracked by IP address
When a system is tracked by IP address and the system is swapped, the easiest way is to give the
new system the same IP address and connect it to the network. If a Configuration Backup was done of
the previous system, a Configuration Restore can now be done to restore all previous settings and
phonebooks.
If the new system is configured with a new IP address,
1. Insert the new IP address in the Connection tab for that system in Systems > Navigator in
Cisco TMS
2. Click Save/Try.
Note: Verify that the SNMP community name is correct, or else this will not work.
System tracked by Host Name
When a system is tracked by the Host Name and the system is swapped, the new system should be
configured with the same host name. If a Configuration Backup was done of the previous system, a
Configuration Restore can now be done to restore all previous settings and phonebooks.
If the new system is configured with a new Host Name,
1. Insert the new Host Name in the Connection tab for that system in Systems > Navigator in
Cisco TMS
2. Click Save/Try.
Note: Verify that the SNMP community name is correct, or else this will not work.

Adding systems
Cisco TMS Administration Guide Page 14 of 37
System tracked by MAC address
When a system is tracked by MAC address, Cisco TMS relies on traps from the endpoint containing
the (new) IP address of the system and the MAC address. If the IP address has changed (which
happens when using DHCP), Cisco TMS will update the IP address in the database to the new IP
address. Cisco TMS will then be able to contact the system.
When swapping a system with a new system, the MAC address will change. If Cisco TMS is tracking
the system by the MAC address, the MAC address in Cisco TMS therefore needs to be updated.
This can be done in two ways:
1. Update the MAC address field in the Connection tab for the system with the new system’s MAC
address, click Save/Try, and reboot the system via the remote control or telnet. This will make the
endpoint send a trap to Cisco TMS with its MAC address and IP address, resulting in Cisco TMS
recognizing the MAC address and updating the IP address in Cisco TMS.
2. Set Track system on network by to IP Address and update the IP address to the new IP
address of the system. Click Save/Try to allow Cisco TMS to read the new MAC address, and set
Track system on network by back to MAC Address.
If a Configuration Backup was done of the previous system, a Configuration Restore can now be done
to restore all previous settings and phonebooks.
Note: Verify that the SNMP community name is correct or else this will not work.

Support for remote systems
Cisco TMS Administration Guide Page 15 of 37
Support for remote systems
From Cisco TMS 11.5, remote systems are supported for booking, getting software upgrades,
receiving phonebook and being part of the statistics created in Cisco TMS. The following section
describes how this feature works and answers some frequently asked questions.
Cisco recommends that the remote system is on a DNS compatible network to ensure proper
communication between Cisco TMS and the remote system.
Before you can use a system as a remote system in Cisco TMS, you must be sure to have set a public
DNS address on the Cisco TMS server. This can be done in Administrative Tools > Configuration >
Network Settings in the pane Advanced Network Settings for Systems on Public Internet/Behind
Firewall. Make sure that this address is reachable from the remote system, if you enter a fully
qualified host name the remote system needs to have its DNS settings in order.
How the communication works
A remote system can either be located publically on the Internet or behind a firewall. The way Cisco
TMS communicates with these two differs slightly.
Reachable on public Internet
Having the system set to Reachable on Public Internet as System Connectivity will make Cisco TMS
communicate with the system in the same way as it does with the systems internally. (To set System
Connectivity, go to on the system in System Navigator > Connection Tab.) However, since the
system cannot contact TMS on TMS’s internal DNS name or IP address, TMS will set a different
address for the phonebook service and feedback on the endpoint. The address used is the one listed
under Administrative Tools > Configuration > Network Settings > Advanced Network Settings
for Systems on Public Internet/Behind Firewall, the field TMS Server Address (Fully Qualified
Host Name or IPv4 Address).
When the system is reachable on the public Internet, you can have TMS communicate with the system
on both HTTPS (port 443) and HTTP (port 80).
Behind firewall
Setting Behind firewall as System Connectivity will make TMS communicate with the endpoint in
much the same way as Reachable on Public Internet, except TMS will not be able to tell the endpoint
to dial and must therefore set up a route where for example a Cisco TelePresence MCU is calling to
the endpoint. All communication between the system and TMS will be HTTP over port 80 or HTTPS
over port 443.
Cisco TMS will automatically detect that a system is a SOHO system when the IP address the
endpoint reports in status.xml is different from the IP address the HTTP packets are coming from, and
the HTTP (port 80) and HTTPS (port 443) ports are closed. Cisco TMS will then set System
Connectivity to Behind Firewall.
Plugging in at remote location
When a system is plugged in at a remote location, it will contact Cisco TMS either with a register event
or a boot event depending on whether the system is already in Cisco TMS. For information on how to
add a remote system to Cisco TMS, see the section Adding a remote system to Cisco TMS.
When Cisco TMS gets this event, it will reply with an acknowledgement and ask to get three files from
the endpoint: ‘status.xml’, ‘history.xml’ and ‘configuration.xml’. It will also check whether any software
upgrade has been scheduled for the endpoint, and if so, perform this.
After 60 seconds, the system will communicate with Cisco TMS, which will set the feedback
expression on the system enabling it to send events.
Cisco TMS will also set the endpoint to contact the Cisco TMS server every 15 minutes.
This will be the heartbeat that allows for communication between the Cisco TMS server and the
remote system, and any change that is done on the remote system or in Cisco TMS will be
synchronized through this heartbeat.

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.
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:
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.
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.
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.
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.

Support for remote systems
Cisco TMS Administration Guide Page 17 of 37
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 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 (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.
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.
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.
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:
Alternative: Description
Put the Cisco TMS in
public This option provides less security, and makes the Cisco TMS vulnerable for attacks directly over the Internet.
Put the Cisco TMS in
DMZ This option provides a bit more security. Port 80 (HTTP) needs to be open in 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.
•/tms/public/external/management/systemmanagementservice.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
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.
The Cisco TMS server in the DMZ should only be accessible on port 80 from
the Internet, and can also 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
TMS server will require db_owner permissions to the tmsng database), and
to disable the XP_CMD_SHELL command on the SQL server for security
reasons.
All Cisco TMS services on the Cisco TMS server in the DMZ must be
disabled to prevent the Cisco TMS server in the DMZ from trying to contact

Support for remote systems
Cisco TMS Administration Guide Page 18 of 37
Alternative: Description
systems on the inside.
Have two Cisco TMS
servers, one for
internal and one for
public systems
This is the most secure option, but will remove some of the features as well
as complicate the usage. The booking will be limited since internal and
external systems are now in two different databases. The two databases will
also cause a problem for statistics as the remote systems will have its
statistics stored on the public Cisco TMS and the internal systems will have
its statistics stored on the internal Cisco TMS. System upgrades will need to
be scheduled separately, and software packages must be put on the two
servers. Phonebooks can however be centralized using an LDAP server that
is available for the two servers. For more information, see the chapter Cisco
TMS features.

User permissions
Cisco TMS Administration Guide Page 19 of 37
User permissions
User Administration
User Administration controls which users have permissions to which parts of Cisco TMS. Permissions
are controlled on a group level (for example, you assign permissions to a group). The total permission
level for an end user will then be the sum of all the permissions assigns to all the groups that the end
user is a member of.
Note: An end user can be (and in most cases is) a member of several groups.
There are three pre-defined groups in Cisco TMS:
Site Administrator
The Site Administrator group has full access to all functions, folders and systems in Cisco TMS. Only
people who could be made responsible for Cisco TMS functioning properly should be members of this
group. Only the site administrator has the rights to edit the Configuration pages under
Administration Tools. For example, only site administrators can change the IP address of the server
and alter the option keys.
Video Unit Administrator
The Video Unit Administrator (VUA) group has full administrative rights to all video conferencing
systems (including gateways, gatekeepers and Cisco TelePresence MCU) in your network. Typically,
the technical engineers are members of this group. Video unit administrators do not have the rights to
edit the Configuration page;otherwise, they have the same rights as the Site Administrator.
Users
All users automatically become members of the Users group. It is recommended that the access
rights assigned to this group represents the lowest level you want any person in your organization to
have. This applies both to what Cisco TMS functions you want them to see and to which systems they
are allowed to use.
Note: You are not allowed to change any of the permission rights for the Site Administrator group.
Also, you cannot add or remove users belonging to the Users group, as all users by default are
members of this group.
User Information and preferences
The first time a user accesses Cisco TMS, the Windows Username of the user is automatically
detected, if configured in Administrative Tools > Configuration > Network Settings. A new Cisco
TMS user is then added automatically. Cisco TMS will also try to detect new user information such as
email address, first and last name through Active Directory lookup. If the information is not available,
the user will be prompted to fill in user information and user preferences in a popup window, as listed
in the table below. First name, last name and email address must be filled in at first logon to the Cisco
TMS server.
User Information Preferences
Windows Username
Your username on the Cisco TMS server. This is automatically detected
by the Internet Information Server. This information can only be
changed by an administrator.
First Name
The user’s first name.
Last Name
The user’s last name.
E-mail Address
The email address that meeting bookings and event notifications should
be sent to.

User permissions
Cisco TMS Administration Guide Page 20 of 37
User Information Preferences
The format must be [e-mail].
Language
This setting lets the users select between 20 different languages in
Cisco Scheduler, where six of the languages also affect the rest of
Cisco TMS (English, Simplified Chinese, Japanese, Korean, Russian
and French.) English is the default language for Cisco TMS so that
users who select, for example, Swedish as the language, they will get
the Scheduler presented in Swedish and the rest of Cisco TMS in
English.
Office Telephone
The user’s office telephone number
Mobile Telephone
The user’s mobile telephone number
Primary System
The user’s preferred video system.
Web Conference
Username
The username for accessing the web conference account
Web Conference
Password
The password for accessing the web conference account
SIP URI:
This is the user’s SIP URI. This field is used by the Cisco LCS
integration. The SIP URI is automatically retrieved from AD if the AD
lookup is properly configured in Cisco TMS.
Time Zone
This setting is used to present the correct time and date information for
the users in Cisco Scheduler (if the client is on a different location than
the Cisco TMS server).
IP Zone
This field allows users to select an IP zone where they are situated.
This IP zone is used when a user books a meeting with only dial-in
participants, to ensure that the Cisco TelePresence MCU that is closest
to the user is picked.
Number of last used
systems listed
This option lets the user choose how many of the previously used
systems should be shown when booking a meeting in Cisco TMS.
First page for New
Conference in Scheduler
Lets the user choose whether to start with the “default page”, the
“choose conference room page” or the “choose time page” when
opening Scheduler.
List your meetings when
opening Cisco Scheduler
Lets the user choose whether all of their meetings should be listed
when accessing Cisco Scheduler
Limiting access to Cisco TMS/Locking out a set of users
Cisco TMS is running on top of Microsoft Internet Information Server and is therefore also utilizing the
Windows user structure for authentication. If the Cisco TMS server is part of a domain, Cisco TMS will
look up any new and existing users in the Active Directory or the local users to see if the users have
the proper permissions to access the Cisco TMS server. If the user has access to the server, they will
also get access to Cisco TMS, and automatically become members of the user groups defined in
Default Groups. When Cisco TMS is installed the first time, all new users will become members of the
Site Administrator group. This should be changed as soon as possible. By setting Default Groups to
Users and limiting the access of the group Users, you can deny access to Cisco TMS to all new
users, even if they are allowed to access the server through the user permissions. A Video Unit
Administrator can then grant each new user the proper permissions by adding them to a new custom
defined group.
Groups
Go to Administrative Tools > User Administration > Groups. This is where you view, edit and set
permissions for Cisco TMS user groups.