Cisco Unified MeetingPlace

MeetingPlace Web Browser Test and Browser Optimization

Document ID: 64465

Updated: Jan 31, 2006



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.

Before You Begin


There are no specific requirements for this document.

Components Used

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.

Edit the Registry Branch

Complete these steps in the registry branch:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
  1. Modify two registry keys:

    • MaxConnectionsPerServer - type DWORD, value = 20

    • MaxConnectionsPer1_0Server - type DWORD, value = 20

  2. Add one registry key:

    • ReceiveTimeout - type DWORD, value = 300000

Related Information

Updated: Jan 31, 2006
Document ID: 64465