Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.2)
Page 19 of 89
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 >
Secure Yes 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 Cisco Collaboration Meeting Rooms Hybrid
The dial out sequence on conference start has changed so that the WebEx participant is the last one to be
connected.
connected.
Improved support for TelePresence Server CDRs
Cisco TMS now uses an improved TelePresence Server API to collect Call Detail Records (CDRs), making
‘Remote Site’, ‘Call Direction’ and ‘Call Protocol’ data available in the CDRs. This feature requires
TelePresence Server version 4.0.
‘Remote Site’, ‘Call Direction’ and ‘Call Protocol’ data available in the CDRs. This feature requires
TelePresence Server version 4.0.
Call Detail Record cause codes for endpoints running Cisco TelePresence TC & TE software
In
Reporting > Call Detail Record > Endpoint
, when receiving a non-standard disconnection cause code
from an endpoint running Cisco TelePresence TC or TE software, Cisco TMS previously mapped it to -1 in
the call detail record. Now any cause code sent by a TC or TE endpoint is displayed in Cisco TMS with 1000
added to the number.
the call detail record. Now any cause code sent by a TC or TE endpoint is displayed in Cisco TMS with 1000
added to the number.