Cisco Cisco Collaboration Server Dynamic Content Adapter Release Notes
18
Release Notes for Cisco Dynamic Content Adapter Release 2.01
Known Caveats
Conditions: Occurs on AOL 6.0/Windows 95 platforms. This results from a timing issue in the AOL
6.0/Windows 95 platform that leaves the window blank and stops the execution of JavaScript calls in the
newly opened window. This problem applies equally to shared content being applied as it does to the
user actively clicking a link to open the window. Errors may occur at any stage (opening or closing the
window) because of the timing problem.
6.0/Windows 95 platform that leaves the window blank and stops the execution of JavaScript calls in the
newly opened window. This problem applies equally to shared content being applied as it does to the
user actively clicking a link to open the window. Errors may occur at any stage (opening or closing the
window) because of the timing problem.
Workaround: Always specify a location (URL) in window.open events OR avoid sharing popups with
callers using AOL 6./Windows 95 OR share only specific popups which specify the desired URL in the
window.open() calls OR disable popup window sharing in general. (See "Users receive a JavaScript
Error when closing popup windows" CSCma19130 for more.)
callers using AOL 6./Windows 95 OR share only specific popups which specify the desired URL in the
window.open() calls OR disable popup window sharing in general. (See "Users receive a JavaScript
Error when closing popup windows" CSCma19130 for more.)
Cisco Tracking Number: CSCma19666
Session-Related Issues
New DCA session created when both agent and caller(s) exit and log back in to CCS
Symptom: If both the agent and caller(s) in a CCS MeetMe session are forced to re-login to CCS (for
example, due to concurrent browser crashes or if both closed their CCS Desktop browser windows) they
are automatically entered into a new DCA session (with a new session ID), rather than the existing one.
The last shared page is not automatically restored and any state information accumulated during the last
session is lost.
example, due to concurrent browser crashes or if both closed their CCS Desktop browser windows) they
are automatically entered into a new DCA session (with a new session ID), rather than the existing one.
The last shared page is not automatically restored and any state information accumulated during the last
session is lost.
Conditions: Only occurs when both agent AND caller(s) are forced to log back in to CCS.
Workaround: None
Cisco Tracking Number: CSCma19974
Incorrect PC clock setting can cause the DCA participant cookie to expire prematurely
Symptom: DCA participant cookies expire based on a configurable timeout. If a user's PC clock setting
is too fast, or if the user's time zone setting is incorrect, the cookie may expire prematurely. In turn, this
can result in a new DCA session being created each time the user makes a subsequent request to the
DCA.
is too fast, or if the user's time zone setting is incorrect, the cookie may expire prematurely. In turn, this
can result in a new DCA session being created each time the user makes a subsequent request to the
DCA.
Workaround: You can adjust the cookie timeout period by editing the ParticipantTimeout property in the
Proxy.properties file.
Proxy.properties file.
Cisco Tracking Number: None
Other Issues
Users' browsers are not mapped until they request content through the DCA
Symptom: Browser mapping may not reflect the browsers of all users in session.