Release Notes
Open issues
Cisco TelePresence Conductor Release Notes (XC2.3.1) Page 14 of 21
Open issues
The following issues apply to this version of the Cisco TelePresence Conductor.
Identifier Description
CSCun63044 Symptom: The Conductor documentation does not describe in detail how the implementation of
syslog works. There is no documentation as to what messages match what facilities.
Versions affected: XC1.2 or later
Workaround: None
CSCud02050 Symptom: If a Lecture-type conference is created on the Conductor with an auto-dialed Content
Server, the recording device is started as soon as the user dials in, even before they have
successfully entered their PIN. If the user disconnects without entering any PIN code, the auto-
dialed content server stays in the conference and records for the maximum time defined in the
template. This occurs even when on Conductor, under Conference configuration > Auto dialed
participants the option 'Keep conference alive' is set to 'No', which means that the conference
should automatically end when only this auto-dialed participant remains. In practice the auto-
dialed participant will only clear when the last participant actually leaves the conference, after
they have joined successfully.
Versions affected: XC1.2 or later
Workaround: Ensure that there is a maximum duration on any conferences that is may affect, so
that the auto-dialed participant is not left recording forever.
CSCuf34880 Symptom: TelePresence Conductor may wait up to 30 seconds before releasing resources
between conferences. This can potentially cause the following two issues:
n it can cause a lack of resources with back-to-back scheduled conferences
n it can cause the overall utilization of the TelePresence Conductor to go up when a participant
repeatedly leaves and joins an ad hoc conference, resulting in the participant eventually not
being able to join back into the conference any more
Versions affected: XC2.0 or later
Workaround: None
CSCui42822 Symptom: Conductor does not properly load balance multiple scheduled meetings beginning at
the same time across multiple TelePresence Servers in a bridge pool. This can lead to situations
where one TelePresence Server will fill up and calls are rejected while other TelePresence
Servers in the same bridge pool are under-utilized.
Versions affected: XC2.0 or later
Workaround: Only add a single TelePresence Server to the bridge pool used for scheduling.
CSCui42818 Symptom: Conductor does not properly load balance multiple scheduled meetings beginning at
the same time across multiple MCUs in a bridge pool. This can lead to situations where one
MCUwill fill up and calls are rejected while other MCUs in the same pool are under-utilized.
Versions affected: XC1.2 or later
Workaround: Only add identical capacity MCUs to a bridge pool and configure either a content,
chairperson or cascade port on the conference template.
Limitations
Full capacity TelePresence Conductor version XC2.3.1 supports: