Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Open issues
Cisco TMS Release Notes (14.3.1)
Page 41 of 49
Identifier
Description
CSCua60131
Added event-stats.txt, log-TMSAgent-console.txt and phonebook-stats.txt to the logs
downloaded when clicking on
downloaded when clicking on
Administrative Tools > TMS Server Maintenance > TMS
Diagnostics >
Download Log Files.
CSCtw61027
Added the option to use a port other than 25 for SMTP server communication.
It is now possible to add :<port number> after the SMTP server name under
Administrative
Tools > Configuration > E-mail Settings >
SMTP Server.
CSCtr90501
Resolved the issue where event notification emails were not received when more than one
email address was entered in
email address was entered in
Administrative Tools > Configuration > Network Settings >
Event Notification >
E-mail Addresses to Receive System and Network Notifications.
Open issues
The following issues apply to 14.3.1 of Cisco TelePresence Management Suite:
Identifier
Description
CSCtr53461
Removing an MCU from one meeting occurrence in a recurrent series still shows the MCU as
being in that conference in the
being in that conference in the
List Conferences
page.
CSCuc98305
The Take Snapshot button does not appear in
Systems > Navigator
even though the system
selected supports this feature.
CSCua17474 In
Conference Control Center >
select a conference
>
Settings, the Recording field incorrectly
displays the options available to the logged in user, not the conference owner.
CSCtt45102
Not possible to make changes to a recurrent series when a participant that has been removed
from the series is part of a new booking that overlaps the first series.
from the series is part of a new booking that overlaps the first series.
CSCua16195 Overlapping conferences booked using the Cisco TMSBA could result in a dial in number conflict.
CSCua51358 Cisco TMS incorrectly reports CTS and TX endpoint status as 'Not registered with Unified CM'.
CSCuc50556
Cisco TMS allocates the wrong dial in number for the allocated port on the MCU.
CSCuc58823
Folder and system permissions do not work correctly.
CSCud10006 Cisco TMS overwrites too many settings when setting phonebooks on Polycom HDX/VSX
systems.
CSCud66234 Inconsistencies with Call Detail Records when using billing codes.
CSCue18466 Cisco TMS does not resolve systems correctly. For example, if endpoint A and endpoint B are
connected to the same MCU conference, attempting to mute or disconnect endpoint A actually
mutes or disconnects endpoint B. This occurs only when using an E.164 dial plan.
mutes or disconnects endpoint B. This occurs only when using an E.164 dial plan.
CSCue26779 Cisco TMS consumes ports after a conference has been moved to a different MCU. This only
occurs for recurrent conferences, if an instance is moved to a different MCU.
CSCuf21982
Cisco TMS changes the call direction to dial in when scheduling an One Button To Push
conference using a dial out Participant Template.
conference using a dial out Participant Template.
CSCuf34881
It is not possible to remove a large number of event notifications for a user in a single operation.
CSCuf81178
It is not possible to move a participant to an Operator Conference if Cisco TMS is configured with
a setup/teardown buffer of more than 3 minutes.
a setup/teardown buffer of more than 3 minutes.