Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved caveats
Scheduler
Reference ID
Summary
86606
Improvement made to Cisco TMS Scheduler. A hierarchical phonebook was not displayed
correctly. The folder structure was flat instead of nested.
The child folder will now be indented displaying the relationship to the parent folder.
correctly. The folder structure was flat instead of nested.
The child folder will now be indented displaying the relationship to the parent folder.
89419
Resolved issue where the Cisco TMS Scheduler failed to add a participant to an instance of a
recurrent conference series if the system was in use in another instance of another recurrent
series.
recurrent conference series if the system was in use in another instance of another recurrent
series.
86470
Resolved issue where the Cisco TMS Scheduler ignored the Default Conference Recording
Alias option of the Conference Settings.
Alias option of the Conference Settings.
89619
Resolved issue where the Cisco TMS Scheduler unchecked the Recording check box if the
user clicked the Previous link.
user clicked the Previous link.
89031
Resolved issue where the Cisco TMS web interface gave conflicting information about
whether the conference was going to be recorded or not if the booking was made through the
Cisco TMS Scheduler.
whether the conference was going to be recorded or not if the booking was made through the
Cisco TMS Scheduler.
Phone Books
Reference ID
Summary
85570
Resolved issue where the buttons named Connect, Update and Disconnect weren’t
displayed under the Sources tab when creating a new phonebook (Phone Books > Manage
Phone Book, New, enter phonebook name, click Save). Only Manage Phone Book Source
was displayed.
displayed under the Sources tab when creating a new phonebook (Phone Books > Manage
Phone Book, New, enter phonebook name, click Save). Only Manage Phone Book Source
was displayed.
115099
Added handling of Phonebook Server Type for TC software endpoints managed by Cisco
TMS.
TMS.
88859
Resolved issue where the TMSSchedulerService tried to synchronize phonebooks with the
TMS Agent even though the TMS Agent was disabled. This lead to errors incorrectly being
reported in the Phonebook Sources Activity Status page.
TMS Agent even though the TMS Agent was disabled. This lead to errors incorrectly being
reported in the Phonebook Sources Activity Status page.
149823
Resolved issue where Cisco TMS sent an empty phonebook to systems having a blank
network address if the phonebook consisted of entries containing IP addresses.
network address if the phonebook consisted of entries containing IP addresses.
Booking
Reference ID
Summary
85222
Resolved issue where Cisco TMS added a T1 system as a T3 system into a conference
booking set up for TelePresence systems including a TelePresence server. The result was
that the call was set up incorrectly.
booking set up for TelePresence systems including a TelePresence server. The result was
that the call was set up incorrectly.
85949
Resolved issue where an MCU was always chosen to host a point to point call for endpoints
that did not have SIP enabled. The MCU was chosen even if External MCU Usage in
Routing (Administrative Tools > Configuration > Conference Settings) was selected with
either Only if needed or Always except point to point.
that did not have SIP enabled. The MCU was chosen even if External MCU Usage in
Routing (Administrative Tools > Configuration > Conference Settings) was selected with
either Only if needed or Always except point to point.
86975
Resolved issue where conferences that were exceptions to a recurring series didn’t start in
Cisco TMS. The problem occurred when a recurring meeting was booked and one of the
meetings was on a different day to the rest of the meetings. This meeting failed to start.
Cisco TMS. The problem occurred when a recurring meeting was booked and one of the
meetings was on a different day to the rest of the meetings. This meeting failed to start.
87301
Resolved issues where an incorrect error was displayed when making a booking. The
incorrect error stated that the systems where already booked. The actual problem was that
there was no available route. As an example, there was not an MCU available to host a call.
This behavior could be seen when editing a booked conference. The original conference had
2 participants but the user added a third or more systems to the call. The conference required
an MCU but there were none available.
incorrect error stated that the systems where already booked. The actual problem was that
there was no available route. As an example, there was not an MCU available to host a call.
This behavior could be seen when editing a booked conference. The original conference had
2 participants but the user added a third or more systems to the call. The conference required
an MCU but there were none available.