Tandberg TELEPRESENCE MANAGEMENT User Manual

Cisco TelePresence

Management Suite

Administration Guide

D13741.12

December 2010

Cisco TMS Administration Guide Page 1 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

Cisco TMS Administration Guide Page 2 of 37

Introduction

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

Cisco TMS Administration Guide Page 3 of 37

Introduction

Disclaimers and notices ....................................................................................................37

Cisco TMS Administration Guide Page 4 of 37

Introduction

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.

Cisco TMS Administration Guide Page 5 of 37

Zones

ISDN Zone Name

Country/Region

Area Code

To access an outsid

e line for

To access an outside line for

Number of digits to use for

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:

local calls, dial

long distance calls, dial

internal ISDN calls

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.

Specify the name of the ISDN zone.
Choose the country this zone is situated in. This will let

Cisco TMS choose the correct country code and correct
international dialing prefixes.

Specify the area code this zone is situated in. This will let
Cisco TMS choose the correct area code rules

Insert the prefix needed to gain an outside line in this ISDN
zone

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.

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.

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]

Cisco TMS Administration Guide Page 6 of 37

Zones

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.

Cisco TMS Administration Guide Page 7 of 37

Zones

IP Zone Name

URI Domain Name:

Gateway Auto Prefix:

Gateway Telephone Prefix:

Gateway 3G Prefix:

Dial-in ISDN Number:

Dial-in ISDN Number for

Allow IP

-

ISDN

-

IP:

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

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

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.

Specify the prefix to use to get an outside ISDN line through the
gateway for video calls.

Specify the prefix to use to get an outside ISDN line through the
gateway for telephone calls.

Specify the prefix to use to get an outside 3G line through the 3G
gateway for 3G calls.

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.

Specify the TSC4 number that will be used for dialing into endpoints or

3G:

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.

Cisco TMS Administration Guide Page 8 of 37

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

Field Description

Prefer IP calls to specific

to a minute.
Systems in the same IP zone will always prefer to dial each other on

IP zones:

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.

Zones

Cisco TMS Administration Guide Page 9 of 37

Adding systems

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.

Cisco TMS Administration Guide Page 10 of 37

Adding systems

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.

Cisco TMS Administration Guide Page 11 of 37

Adding systems

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.

Cisco TMS Administration Guide Page 12 of 37