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 60 of 90
Resolved in 14.3.2
The following issues were found in previous releases and were resolved in 14.3.2:
Booking
Identifier
Description
CSCul42930
Resolved the issue where a dial-in endpoint joined a conference using the IP bandwidth set for
the conference despite having a lower bandwidth set for the endpoint when booking the
conference.
the conference despite having a lower bandwidth set for the endpoint when booking the
conference.
CSCul33187
Resolved the issue where it was not possible to schedule a conference of Type: No Connect with
systems that were behind a firewall.
systems that were behind a firewall.
CSCul35748
Resolved the issue where Cisco TMS repeatedly added the same participants to a conference.
This occurred with SIP dial-out participants that did not contain a domain suffix. This occurred
most frequently for conferences hosted on a TelePresence Conductor deployed in Cisco VCS
B2BUA mode.
This occurred with SIP dial-out participants that did not contain a domain suffix. This occurred
most frequently for conferences hosted on a TelePresence Conductor deployed in Cisco VCS
B2BUA mode.
CSCuh32674 Resolved the issue where it was not possible to create conferences with ISDN dial-in and dial-out
participants when scheduling with TelePresence Conductor.
CSCuf21982
Resolved the issue where a dial-out participant template was changed to a dial-in participant
when added to a One Button to Push conference.
when added to a One Button to Push conference.
CSCuj60215
Resolved the issue where booking a recurrent conference on a date where DST changed at
midnight in the logged in user's time-zone generated an error.
midnight in the logged in user's time-zone generated an error.
CSCuj47583
Resolved the issue where it was not possible to add audio participants with country code +382 for
Montenegro to a conference. The error: 382 is not a valid country code was displayed.
Montenegro to a conference. The error: 382 is not a valid country code was displayed.
Routing
Identifier
Description
CSCul86790
Resolved the issue where adding a participant to an existing conference that was booked by
adding the MCU manually, where the capacity of the MCU was already full, did not reroute to an
MCU with more capacity, which it should have done to accommodate the extra participant.
adding the MCU manually, where the capacity of the MCU was already full, did not reroute to an
MCU with more capacity, which it should have done to accommodate the extra participant.
CSCul30272
Resolved the issue where Cisco TMS did not choose a Cisco TelePresence MCU MSE 8510 to
host a conference when that was the most appropriate routing choice and all the participants were
in the same IP zone as that MCU.
host a conference when that was the most appropriate routing choice and all the participants were
in the same IP zone as that MCU.
CSCuc45195 Resolved the issue where Cisco TMS did not add a bridge to a conference that was escalated
from point to point to three or more participants, when
Administrative Tools > Configuration >
Conference Settings >
External MCU Usage in Routing was set to Always, except point to point..
This occurred if the main participant had a multisite key.
CSCuj57675
Resolved the issue where automatic MCU failover did not work.
CSCul17740
Resolved the issue where Cisco TMS disconnected ad hoc calls when a scheduled One Button
to Push (OBTP) conference was about to start. This occurred for all participants scheduled in the
OBTP conference, even if the ad hoc call was between the scheduled participants.
to Push (OBTP) conference was about to start. This occurred for all participants scheduled in the
OBTP conference, even if the ad hoc call was between the scheduled participants.