TANDBERG TELEPRESENCE MANAGEMENT SUITE - ADMININSTRATION GUIDE 13.0 Administration Manual
TANDBERG TELEPRESENCE MANAGEMENT SUITE - ADMININSTRATION GUIDE 13.0 Administration Manual

TANDBERG TELEPRESENCE MANAGEMENT SUITE - ADMININSTRATION GUIDE 13.0 Administration Manual

Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the TELEPRESENCE MANAGEMENT SUITE - ADMININSTRATION GUIDE 13.0 and is the answer not in the manual?

Questions and answers

Summary of Contents for TANDBERG TELEPRESENCE MANAGEMENT SUITE - ADMININSTRATION GUIDE 13.0

  • Page 1 Cisco TelePresence Management Suite Administration Guide D13741.12 December 2010 Cisco TMS Administration Guide Page 1 of 37...
  • Page 2: Table Of Contents

    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................
  • Page 3 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 ..........................
  • Page 4 Introduction Disclaimers and notices ....................37 Cisco TMS Administration Guide Page 4 of 37...
  • Page 5: Introduction

    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.
  • Page 6: Zones

    Zones 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.
  • Page 7: Area Code Rules

    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;...
  • Page 8: Ip Zones

    Zones IP zones To set up an IP Zone: Go to Administrative Tools > Locations > IP Zones. Click New. 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.
  • Page 9 Zones Field Description to a minute. Prefer IP calls to specific 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.
  • Page 10: Adding Systems

    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.
  • Page 11: Feedback From Cisco Tms When Adding Systems, Rooms And Equipment

    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.
  • Page 12: How Pre-Registration Works

    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.
  • Page 13: Swap A System In Cisco Tms

    Adding systems 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).
  • Page 14: System Tracked By Mac Address

    Adding systems 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.
  • Page 15: Support For Remote Systems

    Support for remote systems 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.
  • Page 16: Adding A Remote System To Cisco Tms

    Support for remote systems 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.
  • Page 17: Software Upgrade

    Support for remote systems 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.
  • Page 18 Support for remote systems Alternative: Description systems on the inside. Have two Cisco TMS This is the most secure option, but will remove some of the features as well servers, one for as complicate the usage. The booking will be limited since internal and internal and one for external systems are now in two different databases.
  • Page 19: User Permissions

    User permissions 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.
  • Page 20: Limiting Access To Cisco Tms/Locking Out A Set Of Users

    User permissions User Information Preferences The format must be xxx@yyy.zz. This setting lets the users select between 20 different languages in Language 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...
  • Page 21: Access To Different Parts Of Cisco Tms

    User permissions To add a new group, Click New. Fill in the name of the group. Fill in a description for this new group. Cisco TMS supports using Active Directory groups where the group memberships for users are managed through Active Directory (AD) To enable AD groups: Go to Administrative Tools >...
  • Page 22: Default Groups

    User permissions Default Groups Default groups define which groups a new user automatically will be assigned to when logging into Cisco TMS for the first time. By default, all users will be member of the Users group. This cannot be changed;...
  • Page 23: Phone Books

    There is a global setting in Cisco TMS (Administrative Tools > Configuration > General Settings > General Settings pane > TANDBERG System Phone Books) that allows administrators to select whether Corporate Directory, Global Directory, or both should be used in their network. Using both is recommended since this will give the endpoints a failover option.
  • Page 24 Phone Books Endpoints such as Cisco TelePresence System 150 MXP with L1.x or L2.x software. The Cisco TelePresence System 150 MXP only supports the Corporate Directory. Endpoints only supporting the Global Directory (globdir.prm) will have the Global Directory (the globdir.prm) file transmitted to the endpoint over HTTP every time adjustments to the Set on system list are made, and at the intervals specified in the Update Frequency dropdown menu.
  • Page 25: Cisco Tms Features

    Cisco TMS features Cisco TMS features Operator conferences Cisco TMS Conference Control Center supports the concept of Operator Conferences. Operator Conferences are ad hoc created conferences that can be used by conference operators to work with individual participants in a conference outside their normally scheduled call. This means that if a site is having a problem, or has questions, an operator can start a new conference and add themselves and the problem site(s) to the special conference.
  • Page 26 Cisco TMS features Provisioning User Directory and Provisioning information from Cisco TMS via a single or clustered Cisco VCS to endpoint devices such as the E20 and the Movi software client. For more information concerning the use and deployment of the Provisioning, see Cisco Provisioning deployment guide.
  • Page 27: Troubleshooting The Cisco Tms Components

    Troubleshooting the Cisco TMS components Troubleshooting the Cisco TMS components This chapter addresses the different components that Cisco TMS consists of: the five services that are to be running at all times, the Java applet needed to show the monitoring pages, the web server needed to display Cisco TMS as web-pages and the database were all information is stored.
  • Page 28: Symptoms

    – but none of them is related to launching the conference. How to fix 1. Check the logs for symptoms or error messages at c:\Program Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-liveservice.txt on the server. 2. Restarting the service or the Cisco TMS server will normally fix any problem with this service. Cisco TMS Administration Guide...
  • Page 29: Tmsplcmdirectoryservice

    You don’t get any phonebooks on your Polycom endpoints How to fix 1. Check the logs for symptoms or error messages at c:\Program Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-plcmdir.txt on the server. 2. Restarting the service or the Cisco TMS server will normally fix any problem with this service. TMSSchedulerService This service is responsible for launching events at set times.
  • Page 30: Symptoms

    Microsoft Windows’ SNMP Component. 2. Check the logs for symptoms or error messages at c:\Program Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-watchdog.txt on the server. 3. Restarting the service or the Cisco TMS server will normally fix any problem with this service. TMSServerDiagnosticsService...
  • Page 31: Cisco Tms Database Management Service (Optional)

    How to fix Start up the Cisco TMS Database Management Utility and verify the settings in the Automatic Backup page (Start > All Programs > TANDBERG). To automatically install the service, select the Enable automatic backup check box. Note: The Cisco TMS Backup Utility was a separate installation found on the Cisco TMS CD that installed this service.
  • Page 32: Symptoms

    Troubleshooting the Cisco TMS components tms/public Handles Corporate Directory for Cisco endpoints. Handles http traps from Cisco TelePresence System MXP and Cisco TelePresence MCU systems. The virtual directory for this component on the IIS is: http://serverIP/tms/public. This component should have the Directory Security set to Anonymous Access. Handles HTTP traps from Polycom systems.
  • Page 33: How To Fix

    Check that they are pointing to valid directories on the Cisco TMS server. Check that the permission settings are correct according to the list above. Check that the IIS allows for running .net extensions. Logs are found in c:\Program Files\TANDBERG\TMS\wwwTMS\Data\Logs\tmsdebug\log-web.txt on the Cisco TMS server. Java Applet – Monitoring...
  • Page 34: The Database

    Troubleshooting the Cisco TMS components Slow or incomplete loading The applet will normally be finished loading within 5 seconds after the Monitoring link is pressed. If you experience a significantly higher loading time, try the points below: Turn off Caching in Java and delete the existing temporary files. Open the Java Control Panel, Click the General tab.
  • Page 35 It is therefore recommended to use the Cisco TMS Tools application, found under TANDBERG in the Start menu of the Cisco TMS server, to change and verify this information.
  • Page 36: Related Documents

    Related documents Related documents The following table lists documents and web sites referenced in this document. All product documentation can be found on our site. Document reference or location Name D14389.03. Dated May 2010 Cisco TMS Installation Guide D50520.04. December 2010 Cisco TelePresence Implementing Secure Management Cisco TMS Administration Guide Page 36 of 37...
  • Page 37 Disclaimers and notices Disclaimers and notices THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

This manual is also suitable for:

Telepresence management suite

Table of Contents