Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Interoperability
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.6.1)
Page 85 of 90
Feature
Limitation
TelePresence Conductor
scheduling
scheduling
TelePresence Conductor waits up to 30 seconds before releasing resources
between meetings. This may cause denial of inbound and outbound calls for
back-to-back meetings and utilization spikes when participants repeatedly leave
and join a meeting. Bug toolkit identifier: CSCuf34880.
between meetings. This may cause denial of inbound and outbound calls for
back-to-back meetings and utilization spikes when participants repeatedly leave
and join a meeting. Bug toolkit identifier: CSCuf34880.
This limitation will be addressed in coming releases of TelePresence Conductor
and Cisco TMS.
and Cisco TMS.
TelePresence Conductor
scheduling
scheduling
Multiple TelePresence Conductor cluster nodes are not supported in Cisco TMS.
TelePresence Conductor
scheduling
scheduling
Scheduling Cisco TMSPE-generated Collaboration Meeting Rooms is not
supported.
supported.
TSP Audio and meeting
extension
extension
If two meetings are allocated the same TSP audio number by WebEx, Cisco TMS
has no awareness of this when deciding whether to extend the meeting. This
could lead to two conferences containing the same audio participants.
has no awareness of this when deciding whether to extend the meeting. This
could lead to two conferences containing the same audio participants.
Monitoring and reporting
n
Conferences using FindMe and Multiway may cause duplicates in
Conference
Control Center
and
Reporting
.
n
Conferences where participants have been put on hold or have been
transferred may cause duplicates in
transferred may cause duplicates in
Conference Control Center
and
Reporting
.
WebEx
n
Advanced recurrence patterns are not supported for CMR Hybrid. When
booking from the
booking from the
New Conference
page, include WebEx before specifying the
recurrence pattern to display only supported recurrence patterns.
n
Deleting a recurrent meeting series while one instance is ongoing will delete
the meeting in Cisco TMS but not in WebEx. This is because WebEx does not
allow changes to ongoing meetings, this includes deletion.
the meeting in Cisco TMS but not in WebEx. This is because WebEx does not
allow changes to ongoing meetings, this includes deletion.
Collaboration Edge
Cisco TMS does not currently support devices that are behind Collaboration Edge.
Expressway
Cisco Expressway-C and Cisco Expressway-E will display in Cisco TMS with
system type TANDBERG VCS.
system type TANDBERG VCS.
System Type field
Some systems that previously contained TANDBERG in the system type may still
show up as TANDBERG in Cisco TMS. This is primarily based on Cisco TMS
reading the system type directly from the system’s API. In some cases, Cisco TMS
added the system type where one was not available through the API. Therefore,
the name may continue to show up with TANDBERG in the system type.
show up as TANDBERG in Cisco TMS. This is primarily based on Cisco TMS
reading the system type directly from the system’s API. In some cases, Cisco TMS
added the system type where one was not available through the API. Therefore,
the name may continue to show up with TANDBERG in the system type.
Scheduling meetings in
Cisco TMS
Cisco TMS
In some cases, Cisco TMS does not allow to book a recurrence meeting, if it
overlaps with a meeting that is scheduled for 24 hours or more.
overlaps with a meeting that is scheduled for 24 hours or more.
Bug toolkit identifier: CSCux64873.
Interoperability
, where you
can also find interoperability test results for other Cisco TelePresence products.