Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Open issues
Cisco TMS Release Notes (14.3.2)
Page 44 of 52
Identifier
Description
CSCua26066
Resolved the issue where a TMS Connection Error ticket was not generated when Cisco TMS
was unable to communicate with a Cisco Unified CM or a Cisco CTS system.
was unable to communicate with a Cisco Unified CM or a Cisco CTS system.
A ticket will now be generated if communication is lost.
CSCua60189
Resolved the issue where changing the SMTP Server in
Administrative Tools > Configuration
> E-mail Settings
did not correctly update the email server used by Cisco TMS.
This was due to a caching issue whereby Cisco TMS could try to use the old server with the new
server’s username and password.
server’s username and password.
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.2 of Cisco TelePresence Management Suite:
Identifier
Description
CSCul44318
TMS Tools > Configuration >
Cisco TMSPE Database Connection Settings incorrectly accepts a
comma as the port delimiter. This does not, however, set the port and Cisco TMS will not be able
to connect to the Cisco TMSPE database. A colon must be used as the delimiter.
to connect to the Cisco TMSPE database. A colon must be used as the delimiter.
CSCul16991
If
Administrative Tools > Configuration > Conference Settings >
Show Reconnect Message
Box on (Non Master) Endpoints is set to No, the reconnect message is not displayed on any of
the endpoints, including the Master endpoint.
the endpoints, including the Master endpoint.
CSCuj62186
Occasionally, Cisco TMS does not correctly randomize numbers for recording aliases when
scheduling using a Cisco TelePresence Recording Server that is in Gateway Mode. This can
cause simultaneous conferences that are using the same recording alias to merge into the same
recorded stream.
scheduling using a Cisco TelePresence Recording Server that is in Gateway Mode. This can
cause simultaneous conferences that are using the same recording alias to merge into the same
recorded stream.
CSCul81027
Booking > List Conferences >
Delete & Export Log Details throw an error and the deletion or log
export may not occur.
CSCuj12622
Cisco TMS displays an inconsistent recording status for bookings that include a Cisco
TelePresence Recording Server that is a member of a cluster. Both No recording and This
conference will be recorded are displayed.
TelePresence Recording Server that is a member of a cluster. Both No recording and This
conference will be recorded are displayed.
CSCui68087
When a recurring meeting series is edited, any changes made previously to an individual
occurrence in the series are lost.
occurrence in the series are lost.
CSCui48610
If a file based phone book contains incorrect alphanumeric data in a field in the ISDN Number
column, a source using this phone book still displays all contacts. A phone book connected to this
source only displays contacts up to the alphanumeric field.
column, a source using this phone book still displays all contacts. A phone book connected to this
source only displays contacts up to the alphanumeric field.