Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved caveats
Reference ID
Summary
85929
Resolved the issue where a user who needed approval for bookings was able to make a
booking without, by copying a previous booking from Booking > List Conferences.
booking without, by copying a previous booking from Booking > List Conferences.
87656
Resolved issue where Vilnius (Lithuania) was displayed in the time zone – GMT +1:00. The
time zone has been changed to the correct GMT +2:00.
time zone has been changed to the correct GMT +2:00.
89023
Resolved issue where a booking was made from Cisco TMS using a Cisco TelePresence
server. A H.323 prefix was not added when dialing an IP address, causing traversal calls to
fail.
server. A H.323 prefix was not added when dialing an IP address, causing traversal calls to
fail.
89102
Resolved issue where an error was seen when making a booking (Booking > New
Conference) if there was two content servers with the same name or a cluster with the same
name as content server not in cluster.
Conference) if there was two content servers with the same name or a cluster with the same
name as content server not in cluster.
88037
Added option to allow SIP>H.320 in call routing. Previously a SIP to H.320 conferences
needed to use an MCU. The routing also affected ISDN entries, which wasn’t seen in a
phonebook of a SIP only system (such as an E20).
Now calls will route between SIP and H.320 as long as a Gateway has been set up in the
relevant IP zone.
needed to use an MCU. The routing also affected ISDN entries, which wasn’t seen in a
phonebook of a SIP only system (such as an E20).
Now calls will route between SIP and H.320 as long as a Gateway has been set up in the
relevant IP zone.
114315
Resolved issue where Cisco C series endpoints could get an incorrect start time if a setup
buffer was specified when booking through the Cisco TMS web interface.
buffer was specified when booking through the Cisco TMS web interface.
89667
Resolved issue where it was impossible to change a future scheduled conference to No
recording if a Content Server already was added to the booking.
recording if a Content Server already was added to the booking.
85397
Resolved issue where participant templates could not be reused in recurrent conferences
86877
Resolved issue where the iCal attachment in the booking confirmation emails did not contain
time zone information.
Outlook will now display meeting times correctly when a conference series is spanning a
Daylight Saving Time border.
time zone information.
Outlook will now display meeting times correctly when a conference series is spanning a
Daylight Saving Time border.
88879
Resolved issue where the end time bar disappeared from the New Conference page if the
conference spanned two days in UTC (Coordinated Universal Time).
conference spanned two days in UTC (Coordinated Universal Time).
89607
Resolved issue where Cisco TMS incorrectly rejected email addresses ending with .local as
invalid when entered in the Conference Information tab.
invalid when entered in the Conference Information tab.
89269
88868
86605
88868
86605
Improved the booking confirmation templates. Cisco TMS will now include the conference
type in the emails, and allow HTML encoded characters in the templates.
type in the emails, and allow HTML encoded characters in the templates.
86244
Resolved issues with recurrent booking patterns. In previous Cisco TMS versions, using the
“Last” recurrence pattern (for example “The Last Sunday of every 2 months”) didn’t include
the current month in the series. Using an “Every X” pattern (for example “Recur every 1
week(s) on Monday”) didn’t include today, if today was a Monday.
“Last” recurrence pattern (for example “The Last Sunday of every 2 months”) didn’t include
the current month in the series. Using an “Every X” pattern (for example “Recur every 1
week(s) on Monday”) didn’t include today, if today was a Monday.
Provisioning
Reference ID
Summary
85601
Resolved issue where incorrect details were given in the TMS Agent Diagnostics
(Administrative Tools > TMS Agent Diagnostics) If the authentication diagnostic failed, the
text pointed to an incorrect location to resolve the problem.
This has now been changed and the correct details are shown.
(Administrative Tools > TMS Agent Diagnostics) If the authentication diagnostic failed, the
text pointed to an incorrect location to resolve the problem.
This has now been changed and the correct details are shown.
87336
Resolved issue where the TMS Agent on a VCS configured to be IPv4 still attempted to
resolve an IPv6 AAAA DNS lookup for the Cisco TMS hostname. The result was that the
replication failed between Cisco TMS and the Cisco VCS.
The TMS Agent will now check the VCS IP protocols and will only use the active set.
resolve an IPv6 AAAA DNS lookup for the Cisco TMS hostname. The result was that the
replication failed between Cisco TMS and the Cisco VCS.
The TMS Agent will now check the VCS IP protocols and will only use the active set.
85663
Resolved issue where the TMS Agent diagnostic (Administrative Tools > TMS Agent