Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4)
Page 6 of 72
server (the Cisco TMS server) must be provisioned to the endpoint by the Unified CM.
Improvements to migration of endpoints from Cisco VCS- to Unified CM-provisioned
For administrators migrating their call control infrastructure from Cisco VCS to Unified CM, Cisco TMS now
understands that a system being added from a Unified CM was already managed by Cisco TMS.
understands that a system being added from a Unified CM was already managed by Cisco TMS.
If a system that is direct-managed by Cisco TMS is registered to a Unified CM and then imported to Cisco
TMS using
TMS using
Add Systems > From List > Unified CM
, Cisco TMS now recognizes that the two systems are
in fact the same, and replaces the original system with the Unified CM-registered one, so all CDR and future
conference data is retained.
conference data is retained.
Conference Diagnostics
must be run after migrating an endpoint.
Changes to conference encryption logic
Endpoints can now be booked in a secure conference hosted on a bridge or TelePresence Conductor
regardless of their encryption capabilities, as encryption will now be set on the bridge or TelePresence
Conductor as well as on the individual endpoint participants.
regardless of their encryption capabilities, as encryption will now be set on the bridge or TelePresence
Conductor as well as on the individual endpoint participants.
For point-to-point or multisite calls, if
Booking > New Conference >
SecureYes is selected, each leg of the
call must be secure otherwise Cisco TMS will not allow the booking.
Overhaul of the TMS Tools interface
n
An updated user-friendly look and feel.
n
Streamlined modernized layout.
n
Improvements to text strings.
n
It is now possible to specify the database port for both Cisco TMS and Cisco TMSPE in
TMS Tools >
Configuration
in the new Port field.
TelePresence Server content port
Cisco TMS now displays content port information for TelePresence Server and uses this information during
resource calculation. This information is displayed under
resource calculation. This information is displayed under
Systems > Navigator >
select a TelePresence
Server
> Settings > View/Edit Settings > Call Settings >
Total Dedicated Content Ports.
Scheduling for Cisco TelePresence Server and Cisco TelePresence MCU SIP-trunked to Unified CM
It is now possible to schedule conferences hosted on TelePresence Servers and TelePresence MCUs that
are SIP-trunked to Unified CM and in Locally Managed operation mode.
are SIP-trunked to Unified CM and in Locally Managed operation mode.
TelePresence MCUs must run software version 4.5 or later.
Conference bridge Numeric ID Quantity
In
Systems > Navigator >
select a conference bridge
> Settings > Extended Settings
, Numeric ID
Quantity is now limited to a maximum value of 200. Previously the maximum value that could be used was
the total number of ports on the bridge.
the total number of ports on the bridge.
Increasing the maximum value enables extended scheduling of recurrent conferences on the bridge.
TelePresence Server with WebEx Enabled TelePresence
The dial out sequence on conference start has changed so that the WebEx participant is the last one to be
connected.
connected.