Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes

 

Changed behavior 

Cisco TelePresence Management Suite 13.2.1 Software Release Notes 

Page 2 of 11 

The names of systems running TE and TC software have been changed in the Cisco TMS application as follows: 

• 

Cisco TelePresence Personal – systems running TE software 

• 

Cisco TelePresence Group Systems – systems running TC software 

This change will only be seen here: 

• 

 New Configuration Template 

 Filter on system type. 

• 

: reports generated here will reflect the new naming convention. 

The following issues were found in previous releases and were resolved in 13.2.1: 

 

CSCua26054 

Resolved the issue where creating a conference would fail when the number of participants 
required an automatic cascade to three MCUs and Best Impression Distribution was selected. The 
issue also occurred when creating a conference template with the same number of participants. 
This did not occur with dial-in participants, when selecting the MCUs manually, or if using Least 
Cost Routing distribution. 

CSCua09092 

Resolved the issue where an unhandled exception could appear when clicking on 

 Add Participants… This occurred if a large number of conferences had already 

been booked for the day that the booking was attempted, and displayed a stack trace error and an 
error in the log-web.txt file. 

CSCty98098 

Resolved the issue where confirmation emails were not received when booking a One Button To 
Push conference including at least one non-Cisco TMS-managed participant (dial-in, dial-out, 
phone book entry, user).

 

CSCty94156 

Resolved the issue where a SIP conference scheduled on an MCU in Cisco TMS did not register 
as SIP if H323 was disabled on the MCU.  
This happened because SIP registration was dependent on the H323 MCU prefix setup, meaning it 
would fail if H323 was turned off on the MCU. 

CSCtx64185 

Resolved the issue where Cisco TMS did not register SIP participants as taking up resources in 
stored bookings on an MCU, which made it possible to overbook SIP participants on the MCU in 
subsequent bookings.   

CSCty43281 

Resolved the issue where it was not possible to add E20 endpoints to a secure conference from 

 after the conference had been booked and saved. An error was 

generated stating: Secure conference not supported by [endpoint name]. 
It is now possible to add an E20 endpoint to a pre-booked secure conference from the 

.