Document ID: 64465
When a user joins a MeetingPlace Web data conference meeting, MeetingPlace Web runs client-side java applets to determine relevant environment information on the client PC, such as:
OS and version
type of browser and version
java type and version
On certain browsers/versions, the applet also modifies some registry settings to optimize the browser for end-user data conference experience. This is done automatically by the java applets and once optimized, the user is prompted to close and reopen all browsers for the changes to take effect.
Some company IT departments can lockdown the end user workstation to prevent applets from making the necessary optimization changes. For those customers, their IT department can implement those registry changes manually, and inlcude them in their standard corporate PC image build.
There are no specific requirements for this document.
The information in this document is based on these hardware and software versions.
MeetingPlace Web versions 4.2.7.x, 4.3.0.x, and 5.3.x
For more information on document conventions, refer to Cisco Technical Tips Conventions.
Complete these steps in the registry branch:
Modify two registry keys:
MaxConnectionsPerServer - type DWORD, value = 20
MaxConnectionsPer1_0Server - type DWORD, value = 20
Add one registry key:
ReceiveTimeout - type DWORD, value = 300000
- Voice Technology Support
- Voice and IP Communications Product Support
- Troubleshooting Cisco IP Telephony
- Technical Support & Documentation
|Updated: Jan 31, 2006||Document ID: 64465|