Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
New features and functionality in version 13.0
Cisco TelePresence Management Suite Release notes
Page 9 of 25
Viewing the Auto Attendant conference is also new in Cisco TMS 13.
Encryption available on conferences including an MCU
For a conference involving the Cisco TelePresence MCU version 4.1, setting Secure to Yes in
Booking > New Conference > Advanced Settings will now result in the Encryption field for this
conference to be set to Required on the MCU. This requires that all endpoints/systems in the
conference support encryption. By setting encryption to No or If Possible in Cisco TMS, the MCU will
leave the Encryption field as it is configured on the MCU itself.
Booking > New Conference > Advanced Settings will now result in the Encryption field for this
conference to be set to Required on the MCU. This requires that all endpoints/systems in the
conference support encryption. By setting encryption to No or If Possible in Cisco TMS, the MCU will
leave the Encryption field as it is configured on the MCU itself.
Reporting
Cisco TelePresence ISDN Gateway
– CDR
Cisco TMS and Cisco TelePresence ISDN Gateway version 2.1
will allow Call Detail Records (CDR‟s)
to be viewed. Go to Reporting > Call Detail Record > Gateway to view any calls made using the
Cisco TelePresence ISDN Gateway.
Cisco TelePresence ISDN Gateway.
System > Navigator
Recording device
Cisco TMS now shows active IPVCR recordings in the Systems > Navigator > Call Status tab. This
is a new feature and requires IPVCR SW 3.0. An active call will show the name of the recording,
participant name, Call Protocol, Address Duration (seconds) and Call direction.
is a new feature and requires IPVCR SW 3.0. An active call will show the name of the recording,
participant name, Call Protocol, Address Duration (seconds) and Call direction.
IPVCR Video Ports
Cisco TMS now shows the total number of IPVCR video ports available in Systems > Navigator >
Call Settings > Max Number of Active Recordings: This feature requires SW version 3.0 on the
Cisco IPVCR.
Call Settings > Max Number of Active Recordings: This feature requires SW version 3.0 on the
Cisco IPVCR.
MCU cluster type
Cisco TMS will identify the cluster type of a Cisco TelePresence MSE blades running 4.1 and higher.
This will be seen Systems > Navigator > Settings tab > Configuration pane > MCU Cluster Type
field which will display Slave, Master or Unclustered. The field MCU Cluster Type is not possible to
edit. If the Cisco TelePresence MSE blade shows Slave then this MCU cannot be edited and cannot
be booked in a conference.
This will be seen Systems > Navigator > Settings tab > Configuration pane > MCU Cluster Type
field which will display Slave, Master or Unclustered. The field MCU Cluster Type is not possible to
edit. If the Cisco TelePresence MSE blade shows Slave then this MCU cannot be edited and cannot
be booked in a conference.
Cisco TelePresence MSE 8000 supervisor support
Support is added for Cisco TelePresence MSE 8000 supervisor Blade which requires software version
2.1. When adding a new Cisco TelePresence MSE 8000 supervisor Blade into Cisco TMS Systems >
Navigator a list of all blades on the chassis will be displayed, you can then choose to add these
blades into Cisco TMS rather than add them individually.
2.1. When adding a new Cisco TelePresence MSE 8000 supervisor Blade into Cisco TMS Systems >
Navigator a list of all blades on the chassis will be displayed, you can then choose to add these
blades into Cisco TMS rather than add them individually.
Management of the supervisor blade is now possible including ticket handling for chassis alarms such
as fan, power, and slot alarms. You can also view the status of all the blades in the chassis from
Systems > Navigator > Supervisor
as fan, power, and slot alarms. You can also view the status of all the blades in the chassis from
Systems > Navigator > Supervisor
Cisco VCS and Gatekeeper integration
The registration search across clusters is added in the Systems > Navigator > Registrations tab.
Cisco VCS(s) version X6 or greater will show all registrations for the entire cluster and also which peer
the registration is on.
Cisco VCS(s) version X6 or greater will show all registrations for the entire cluster and also which peer
the registration is on.
Note: The search feature applies to registrations on any Gatekeeper (not only Cisco VCS). The
difference is that for Cisco VCS you can go to any cluster member and see all registrations in this tab.
difference is that for Cisco VCS you can go to any cluster member and see all registrations in this tab.