Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.1)
Page 13 of 90
n
Future scheduled conferences in the
Activity Status
page are now shown with the conference title in the
Description column, instead of the conference ID in brackets. Conferences that were scheduled before
the upgrade to 14.5 will still be shown in the old format.
the upgrade to 14.5 will still be shown in the old format.
n
Changed the timestamp date format in the Installer logs to be ISO compliant. The new format is YYYY-
MM-DD.
MM-DD.
n
Localization: Multiple improvements to layout and quality of translated versions of Cisco TMS.
n
Improvements to logging information provided when applying calendars to endpoints. The system ID is
now shown, and communication/authentication problems are not logged as they are visible elsewhere in
Cisco TMS.
now shown, and communication/authentication problems are not logged as they are visible elsewhere in
Cisco TMS.
n
When adding or editing a Cisco TMS user, the following fields are now mandatory:
l
Windows Username
l
First Name
l
Last Name
l
E-mail Address
Removed in this release
Support for the following systems is removed in this release:
n
TANDBERG Movi Server (Movi 1.0 hardware appliance server)
n
TANDBERG 3G Gateway
n
TANDBERG Entrypoint
n
TANDBERG Experia
n
TANDBERG Video Portal
n
Cisco 7985G and other Cisco SCCP video endpoints
n
Cisco Gatekeeper/Multimedia Conference Manager (IOS Gatekeeper)
Support for Internet Explorer 9 is removed in this release. IE9 will probably work with this version of Cisco
TMS but it is no longer a supported browser and was not tested for compatibility.
TMS but it is no longer a supported browser and was not tested for compatibility.
Changed in 14.4.2
Summary of the release
14.4.2 was a maintenance release addressing an issue with duplicate external primary keys, affecting
customers using Cisco TMS Booking API (Cisco TMSBA) clients such as Cisco TMSXE and Cisco
TMSXN. This issue was found in Cisco TMS versions 14.4 and 14.4.1 and causes problems replicating
bookings from Cisco TMS to Microsoft Exchange or IBM Domino.
customers using Cisco TMS Booking API (Cisco TMSBA) clients such as Cisco TMSXE and Cisco
TMSXN. This issue was found in Cisco TMS versions 14.4 and 14.4.1 and causes problems replicating
bookings from Cisco TMS to Microsoft Exchange or IBM Domino.
Technical description of external primary key issue: CSCup76424
In Cisco TMS 14.4 and 14.4.1, Cisco TMS assumes that every conference has a unique ExternalPrimaryKey
value. Under certain conditions, earlier versions of Cisco TMS allowed multiple meetings to share the same
key, and the 14.4 and 14.4.1 upgrade scripts failed to de-duplicate these keys.
value. Under certain conditions, earlier versions of Cisco TMS allowed multiple meetings to share the same
key, and the 14.4 and 14.4.1 upgrade scripts failed to de-duplicate these keys.
Cisco TMSBA clients such as Cisco TMSXE use the ExternalPrimaryKey to retrieve conferences from
Cisco TMS, always expecting to get the same conference when a specific ExternalPrimaryKey is provided
to Cisco TMSBA. If conference A and conference B have the same ExternalPrimaryKey value in the tmsng
database, Cisco TMSBA could return data belonging to conference A when Cisco TMSXE asks for
conference B, and vice versa. If this happens to Cisco TMSXE, the Cisco TMSXE replicator could
permanently delete data from Microsoft Exchange based upon incorrect data returned from Cisco TMSBA.
Cisco TMS, always expecting to get the same conference when a specific ExternalPrimaryKey is provided
to Cisco TMSBA. If conference A and conference B have the same ExternalPrimaryKey value in the tmsng
database, Cisco TMSBA could return data belonging to conference A when Cisco TMSXE asks for
conference B, and vice versa. If this happens to Cisco TMSXE, the Cisco TMSXE replicator could
permanently delete data from Microsoft Exchange based upon incorrect data returned from Cisco TMSBA.