Cisco TelePresence Management Suite
Provisioning Extension 1.6
Software Release Notes
Last Updated: January 2016
Version 1.6
Cisco Systems, Inc.
1
www.cisco.com
Cisco TelePresence Management Suite Provisioning Extension 1.6 Software Release Notes
2
Cisco TelePresence Management Suite Provisioning Extension 1.6 Software Release Notes
Preface
Change History
Table 1 Software Release Notes Change History
Date
Change
Reason
January
2016
Updated Active Meeting Manager section in New In 1.6 for the Display Names for Cisco
TMS - Managed Endpoints description.
Request
December
2015
Updated Active Meeting Manager section in New In 1.6 for the Enable Ad Hoc Conference
Monitoring settings description.
Request
December
2015
Release of Cisco TMSPE1.6.
Introduction
This document describes the main features of Cisco TelePresence Management Suite Provisioning Extension version
1.6, and changes from previous versions.
Product Documentation
The following documents provide guidance on installation, initial configuration, and operation of the product:
■
Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide
■
Cisco TelePresence Management Suite Provisioning Extension with Cisco Unified Communications Manager
Deployment Guide
■
Cisco TelePresence FindMe User Guide
New in 1.6
Active Meeting Manager (Preview Feature)
A new feature, Active Meeting Manager (AMM) has been introduced for hosts to control their Collaboration Meeting
Room (CMR) meetings. AMM is a light-weight meeting management tool, which uses a web browser interface and is
a component of CMR portal page.
To launch AMM, the CMR host clicks the Open Active Meeting Manager button in the CMR portal page (Active
Meeting Manager section).
AMM includes the following features:
■
Participants - Displays a list of active participants in the meeting
■
Mute/Unmute - Mute or Unmute a specific participant
■
Mute/Unmute All - Mute or Unmute all participants
■
Remove - Remove a specific participant
■
Remove All - Remove all participants
If a meeting host uses AMM to mute participants on the bridge, in certain situations it may not be apparent to affected
participants that they are muted, or that they can press *6 on their endpoint to unmute.
3
Cisco TelePresence Management Suite Provisioning Extension 1.6 Software Release Notes
An option Allow Active Meeting Manager has been added in Cisco TMS Portal > Administrative Tools >
Configuration > Provisioning Extension Settings > Collaboration Meeting Room to enable or disable AMM in CMR
portal page.
For details, see the Cisco TelePresence Management Suite Provisioning Extension with Cisco VCS Deployment Guide
(1.6).
The following browsers are recommended to open AMM:
■
■
Windows operating system
— Internet Explorer version 11
—
Mozilla Firefox version 42
—
Microsoft EDGE version 20
MAC operating system
— Mozilla Firefox version 42
AMM functionality works for a CMR host, only if the Enable Ad Hoc Conference Monitoring under Administrative
Tools > Configuration > Network Settings > TMS Services is set to the default value Yes.
Multiple Protocol Support for Call-in Participants
ISDN and IP(H323) protocols support have been added to Video Call-in and Audio Call-in participants in addition to
the existing SIP protocol support. This feature can now be enabled or disabled by the administrator in Administrative
Tools > Configurations > Provisioning Extension Settings > Smart Scheduler.
We recommend to provide additional training to end-users, so that they can understand the usage of protocols in
detail, when multiple protocols are enabled for Smart Scheduler Call-ins.
Support for Java 8
Cisco TMSPE 1.6 supports Java 8 update 66, 32 and 64-bit.
Display Names for Cisco TMS - Managed Endpoints
Cisco TMS uses the description field from the Unified CM endpoint definition as the display name in Active Meeting
Manager (and Conference Control Center). Not the caller ID.
To avoid labeling mismatches, do the following for any Cisco TMS-managed endpoints:
■
If the endpoints are Unified CM-registered, in Unified CM set the endpoint Description field to match the
Display (Caller ID) field.
■
If the endpoints are Cisco VCS- registered, in Cisco TMS, set the Name field to match the Display Name
defined for the endpoint.
More details about provisioning display names are in the CMR Premises Deployment Guide (Unified CM or Cisco VCS
version), Appendix “Provisioning Display Names Across the Solution”.
Identifier CSCux57676 in Bug Search Tool relates to this issue.
Note: If you import endpoint definitions from Unified CM, the Name field for the endpoints is not configurable in Cisco
TMS and is grayed out in the user interface. Use the endpoint Description field in Unified CM instead.
Resolved and Open Issues
Follow the link below to find up-to-date information about the resolved issues in this release:
https://tools.cisco.com/bugsearch/search?kw=*&pf=prdNm&pfVal=283613664&rls=TMSPE1.6&sb=anfr&srtBy=byRe
l&bt=custV
4
Cisco TelePresence Management Suite Provisioning Extension 1.6 Software Release Notes
You need to refresh your browser after you log in to the Cisco Bug Search Tool.
Limitations
Feature
Limitation
Java support
Upgrading Java during operation of this product is not supported.
Caution: Do not upgrade Java while Cisco TMSPE is running. Disable the Windows service
prior to any upgrade. We strongly recommend disabling automatic Java updates on the
server.
Smart Scheduler
Named Pipe
connection issues
using SQL Express
■
The site administrator configured for communication with Cisco TMS will receive an
e-mail notification every time a meeting is booked or updated in Smart Scheduler.
■
Modifying single instances of recurrent meetings is currently not possible in Smart
Scheduler. Series with exceptions created in Cisco TMS or other booking interfaces
may not be modified using Smart Scheduler.
■
Modifying a previously booked meeting series with a computer set to a different time
zone than used for the original booking, will change the recurrence pattern's end date
to use the latest time zone.
In the MSDE mode using the Named Pipe protocol, connection to the database may fail with
the error "The specified network name is no longer available".
The problem is seen on Windows Server 2008, and can be solved with the following hotfixes:
Windows Server 2008 R2:
http://support.microsoft.com/kb/2194664http://support.microsoft.com/kb/2444328
Note that the default connection protocol is TCP/IP.
Dual network
interface not
supported
Like Cisco TMS, this extension does not support the use of two network interfaces. (Identifier
CSCtx52264)
Language settings
In the Self Service Portal, the Language setting for each particular user in Account Settings
does not influence the language setting in Cisco TMS.
McAfee Antivirus
McAfee Antivirus will occasionally corrupt files required for Cisco TMSPE to run.
Disable McAffe Antivirus during install.
Cisco TMSPE fails
to communicate
with Cisco TMS
Cisco TMSPE fails to communicate with Cisco TMS when the new security mode is set to
High in Cisco TMS 15.0.
This limitation will be addressed in forthcoming releases of Cisco TMSPE.
5
Cisco TelePresence Management Suite Provisioning Extension 1.6 Software Release Notes
Feature
Limitation
Active Meeting
Manager
■
Cisco TMSPE 1.6 supports Active Meeting Manager when it runs on Windows Server
2012 R2 64-bit.
■
At present Active Meeting Manager does not work in Google Chrome and Safari
browser and it is being worked on.
■
When the Mute/Unmute and Remove/Remove All operations are done from the
endpoint, currently there may be a delay in the display of status message in AMM.
■
Active Meeting Manager supports only Collaboration Meeting Room conferences and
does not work with scheduled meetings.
■
Depending on your configuration and the number of concurrent meetings at any time,
Cisco TMSPE response times may be degraded, if a significant number of meeting
hosts use the Active Meeting Manager at the same time.
Updating to Cisco TMSPE 1.6
Prerequisites and Software Dependencies
Cisco TelePresence Management Suite Provisioning Extension 1.6 requires:
■
Cisco TMS 15.0 and later.
■
Cisco TMS 15.1 for Active Meeting Manager.
■
Cisco TelePresence Conductor:
— XC4.0 or later version for Multiparty Licensing .
—
XC4.1 or later for Active Meeting Manager.
One or both of the following is also required:
■
Cisco VCS X8.1 or later.
■
Unified CM 9.1.2 or later.
Unified CM 10.5.2 is required for ad hoc calls to support the use of PMP licenses.
For installation instructions, full system requirements, and other prerequisites, see Cisco TelePresence Management
Suite Provisioning Extension Deployment Guide for Cisco VCS or Unified CM.
Migrating from Cisco TMS Agent Legacy
Direct migration to this version of Cisco TMSPE is not supported.
Before upgrading to 1.6, customers running Cisco TMS Agent Legacy must migrate by way of:
■
Cisco TMS 13.2.x
■
Cisco TMSPE 1.0
Instructions for migration can be found in Cisco TelePresence Management Suite Provisioning Extension Deployment
Guide for Cisco TMSPE 1.0 with Cisco TMS 13.2.5
Upgrading from Previous Versions
High-level Workflow
Cisco TelePresence Management Suite Provisioning Extension relies on and integrates with multiple other products.
When upgrading your deployment:
6
Cisco TelePresence Management Suite Provisioning Extension 1.6 Software Release Notes
1. Upgrade Cisco TMS to the required version following the instructions in Cisco TMS Installation and Upgrade
Guide.
2. Upgrade Cisco Cisco TMSPE.
3. Upgrade other systems such as TelePresence Conductor as required.
Upgrading Cisco TMSPE
If the Server is Running Java 7
To upgrade from Cisco TMSPE 1.1 or 1.0 if Java 7 is already installed on the server:
1. Ensure that all critical Windows Updates are installed on your server.
2. Close all open applications and disable virus scanning software.
3. Extract the Cisco TMSPE installer from the zip archive to the Cisco TMS server.
4. Run the Cisco TMSPE installer as administrator.
Follow the installer instructions.
Any existing provisioning and FindMe configurations will be kept when upgrading.
If the Server is Running Java 6
To upgrade from Cisco TMSPE 1.1 or 1.0 if the server is still running Java 6:
1. Uninstall Cisco TMSPE on the server. Do not remove any other files.
2. Install Java 7.
1. Ensure that all critical Windows Updates are installed on your server.
2. Close all open applications and disable virus scanning software.
3. Extract the Cisco TMSPE installer from the zip archive to the Cisco TMS server.
4. Run the Cisco TMSPE installer as administrator.
3. Follow the installer instructions
Using the Bug Search Tool
The Bug Search Tool contains information about open and resolved issues for this release and previous releases,
including descriptions of the problems and available workarounds. The identifiers listed in these release notes will
take you directly to a description of each issue.
To look for information about a specific problem mentioned in this document:
1. Using a web browser, go to the Bug Search Tool.
2. Sign in with a cisco.com username and password.
3. Enter the bug identifier in the Search field and click Search.
To look for information when you do not know the identifier:
1. Type the product name in the Search field and click Search.
2. From the list of bugs that appears, use the Filter drop-down list to filter on either Keyword, Modified Date,
Severity, Status, or Technology.
Use Advanced Search on the Bug Search Tool home page to search on a specific software version.
The Bug Search Tool help pages have further information on using the Bug Search Tool.
7
Cisco TelePresence Management Suite Provisioning Extension 1.6 Software Release Notes
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request,
and gathering additional information, see What’s New in Cisco Product Documentation at:
www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical
documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS
feeds are a free service.
Active Meeting Manager Disclaimer
The Active Meeting Manager (AMM) is provided as a preview feature to the Cisco TelePresence Management Suite
Provisioning Extension (Cisco TMSPE) and Cisco Collaboration Meeting Rooms (CMR) Premises. Use of the AMM is
subject to the software license and limited warranty
http://www.cisco.com/c/en/us/td/docs/general/warranty/English/EU1KEN_.html for TMSPE or CMR Premises. You
should only use AMM in your production environment if your end users’ web browsers support Integrated Windows
Authentication using WebSocket connections. Cisco reserves the right to disable the AMM at any time without
notice. Cisco Technical Support will provide limited assistance to customers who wish to use the AMM as a preview
feature. If you provide feedback regarding AMM (“Feedback”) by emailing such Feedback to [email protected], you agree that Cisco may use for any purpose any Feedback that you provide Cisco regarding
AMM.
Cisco Legal Information
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.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE
INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS
REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR
CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of
California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved.
Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE
SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL
WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING,
USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR
INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA
ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual
addresses and phone numbers. Any examples, command display output, network topology diagrams, and other
figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone
numbers in illustrative content is unintentional and coincidental.
All printed copies and duplicate soft copies are considered un-Controlled copies and the original on-line version
should be referred to for latest version.
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco
website at www.cisco.com/go/offices.
8
Cisco TelePresence Management Suite Provisioning Extension 1.6 Software Release Notes
© 2015 Cisco Systems, Inc. All rights reserved.
Cisco Trademark
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other
countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks
mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
9
Cisco TelePresence Management Suite Provisioning Extension 1.6 Software Release Notes
10