Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Planned changes for future releases
Cisco TelePresence Management Suite 14.1 Software Release Notes
Page 5 of 20
Cisco TMS Installer
The installer no longer enforces a reboot of the Windows Server after an upgrade. The installer now only prompts the
administrator to reboot the server if necessary.
administrator to reboot the server if necessary.
Removed the Call Status page for MCUs
Previously, Cisco TMS allowed users to create ad hoc conferences on MCUs using the
Call Status
page in the
System > Navigator
. These ad hoc conferences were assigned a number that was in the range reserved for
scheduled use by Cisco TMS, and could thus lead to two conferences having the same number.
In Cisco TMS 14.1, it is no longer possible to create new conferences on MCUs using this page.
Protocol priorities when routing scheduled calls
Cisco TMS now prioritizes SIP over dialing an IP address when routing scheduled calls. Cisco TMS still prefers using
H.323 (dialing the H.323 ID or E.164 alias) over SIP.
H.323 (dialing the H.323 ID or E.164 alias) over SIP.
Option for database re-indexing removed
The Re-index database option found under
Administrative Tools > TMS Server Maintenance
has been removed.
Cisco TMS no longer supports automatically re-indexing tables in the tmsng database.
Planned changes for future releases
Third party product support
We plan to withdraw support for the following systems in the next release of Cisco TMS:
Sony PCS1
Polycom Viewstation (1st and 2nd gen)
Polycom iPower
Polycom ViaVideo
VTEL Galaxy
Aethra VegaStar
Rad ViaIP Gateway
Rad ECS GK
Resolved issues
The following issues were found in previous releases and were resolved in 14.1:
Booking
Identifier
Description
CSCua57784
Resolved the issue where One Button To Push conferences with participants added from a phone
book failed.
book failed.
CSCud07712
Resolved the issue where Cisco TMS booked all ports on an MCU type system, even though the
booking was not Reservation Only.
The issue happened when a user edited an existing booking and removed all participants except
the MCU.
booking was not Reservation Only.
The issue happened when a user edited an existing booking and removed all participants except
the MCU.