Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.1)
Page 53 of 90
Identifier
Description
CSCun28043
Resolved the issue where changing the dial plan for an MCU did not invalidate the route in
existing conferences that included that MCU.
existing conferences that included that MCU.
CSCuj62186
Resolved the issue where Cisco TMS occasionally did not correctly randomize numbers for
recording aliases when scheduling using a Content Server that was in Gateway Mode. This
could cause simultaneous conferences using the same recording alias to merge into the same
recorded stream.
recording aliases when scheduling using a Content Server that was in Gateway Mode. This
could cause simultaneous conferences using the same recording alias to merge into the same
recorded stream.
CSCuc50556
Resolved the issue where Cisco TMS allocated the wrong dial in number for the allocated
port on the MCU.
port on the MCU.
CSCum98292
Improved dial-in number allocation for back to back meetings. Cisco TMS is now less likely to
assign the same number for back-to-back meetings when the bridge is close to full capacity.
assign the same number for back-to-back meetings when the bridge is close to full capacity.
CSCuo27217
Resolved the issue where attempting to schedule a Best Impression distribution cascaded
conference caused an infinite loop in Cisco TMS. This occurred if there were a large number of
dial-in participants.
conference caused an infinite loop in Cisco TMS. This occurred if there were a large number of
dial-in participants.
Monitoring
Identifier
Description
CSCun25273
Resolved the issue where using
Conference Control Center
to lock a cascaded conference
locked the conference on the slave MCU but not the master MCU.
CSCun25310
Resolved the issue where muting an endpoint using its own interface was not reflected in
Conference Control Center
, although the endpoint was muted in the conference.
CSCun25471
Resolved the issue where it was not possible to disconnect a participant from a conference
using
using
Conference Control Center
. This occurred if the system name contained an
apostrophe.
CSCum42607
Resolved the issue where accessing the
Conference Control Center
could generate a Java
warning: Do you want to run this application? after updating Java to version 7 update 45 on
the Cisco TMS server. In some environments
the Cisco TMS server. In some environments
Conference Control Center
did not load at all.
CSCuj34799
Resolved the issue where
Conference Control Center
could incorrectly display scheduled
conferences on a TelePresence Conductor as ad hoc conferences with a duration value of 0.
CSCuh57792
Resolved the issue in
Conference Control Center
where layouts on endpoints did not change
if the layout was changed first to a custom layout, then back to Default Family View, then back
to a custom layout.
to a custom layout.
CSCun72842
Resolved the issue where Cisco TMS did not correctly resolve ad hoc conferences hosted on
a TelePresence Server in
a TelePresence Server in
Conference Control Center
. A separate conference was displayed
for each call leg.
CSCue26774
Resolved the issue where moving a conference to a different bridge was not reflected in
Conference Control Center
until the conference was selected on the old bridge.
CSCun72817
Resolved the issue where the conference event log displayed incorrect information about
participants being added to and removed from a conference hosted on a TelePresence
Conductor.
participants being added to and removed from a conference hosted on a TelePresence
Conductor.