Release Notes

Resolved issues
Cisco TelePresence Conductor Release Notes (XC2.3.1) Page 13 of 21
Identifier Description
CSCue89279 Symptom: FUR (Fast picture update) messages get dropped if they contain a stream ID - this
means that no video or blocky video may be seen, especially if the data network drops video
packets.
TS prior to TS3.0(2.46) did not send stream IDs for main video.
Diagnosis: This problem will only be seen if Conductor without this fix in is used with TS >= 3.0
(2.46).
Versions affected: XC2.0 and XC2.0.1
Workaround: Avoid upgrading TS to >= 3.0 (2.46) until Conductor is upgraded.
Resolved in XC2.0.1
The following issues were found in previous releases and were resolved in XC2.0.1:
Identifier Description
CSCud97851 Symptom: Incident report generated. The switchboard process is automatically restarted by the
app so there is a limited impact on the customer.
Diagnosis:
Versions affected: XC2.0
Workaround: None.
Resolved in XC2.0
The following issues were found in previous releases and were resolved in XC2.0:
Identifier Description
CSCub46878 Symptom: Maximum latency for Telepresence Conductor is not documented.
Diagnosis: None.
Versions affected: XC1.2
Workaround: None.
CSCua01811 Symptom: Cannot load "trusted CA certificates file" onto Conductor via the web interface.
Diagnosis: None.
Versions affected: XC1.2
Workaround: Load "trusted CA certificates file" onto Conductor using SCP.
CSCub84541 Symptom: Logins on the web can be slow to complete.
Diagnosis: When remote authentication is enabled, all logins (not just remote users) can be
delayed by many seconds if the LDAP server is slow to respond.
Versions affected: XC1.2
Workaround: None, however delays from the LDAP server are outside the control of the
Conductor.
Additional Information: The fix in X8.0 disables LDAP checks for local users, removing local
user delays. Remote user delays will still exist if the LDAP server is slow to respond, but this is
outside the control of the Conductor.