Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues in 14.1
Cisco TelePresence Management Suite 14.1.1 Software Release Notes
Page 7 of 21
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.
Booking API HTTP GET and POST disabled by default
HTTP GET and POST methods are now disabled by default. This applies only to remote clients, they are still
available to clients on the Cisco TMS server itself.
available to clients on the Cisco TMS server itself.
We recommend that you do not use HTTP GET and POST for security reasons. However, if your booking application
relies on these methods you can:
relies on these methods you can:
Rewrite the application so that it uses SOAP requests.
Re-enable GET and POST using the TMS web.config file.
Resolved issues in 14.1
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.
CSCtz48797
Resolved the issue where the meeting password was not saved for a password protected meeting
when the reservation type was set to Manual Connect.
when the reservation type was set to Manual Connect.
CSCud07690
Removed the non-functioning Details link for external dial in participants in the
New Conference
and
Edit Conference
pages.
Added a tool-tip displaying Name and Direction.
CSCtx51962
Resolved the issue where if a user cancelled an edit of a conference in
Booking >List
Conferences,
the start and end time of the conference changed. When the user entered the
List
Conferences
page again, the start and end time were correct.
CSCua18048
Resolved the issue where conferences created from Microsoft Outlook via Cisco TMSXE defaulted