Limiting participants in a video conference

The default maximum number of participants in a single audio-only or video conferences is set to 20. You can adjust this value to accommodate specific network consumption requirements.

About this task

Network factors affecting audio and video services include bandwidth and latency. The more bandwidth available to the server and the shorter latency will allow more participants per call. The bandwidth to the server is recommended at least 1Gbps (Gigabit per second), and latency from client to server should be less than 150ms.

Environmental conditions affecting audio and video services include server capacity, total number of simultaneous users, selected audio codec and video resolution, expected number of interactive participants, expected number of video participants, and expected number of simultaneous calls. These conditions will effect the limit of the number of participants per call.

Edit the ConferenceManager.properties for every Conference Manager and change the MaximumVideoConferenceUsers value to a number participants appropriate for your network and the environmental conditions at your site.

Procedure

  1. On the server hosting the Sametime® Media Manager Conference Manager, navigate to the following directory:
    WAS_INSTALL_ROOT/profiles/STMSAppProfile/installedApps/cell_name/
           ConferenceFocus.ear/ConferenceFocus.war
  2. Open the ConferenceManager.properties file for editing.
  3. Locate the section shown here:
    #
    # MaximumAudioConferenceUsers is the maximum number of users the service provider supports
     for each audio conference call.
    #
    MaximumAudioConferenceUsers=20
    
    #
    # MaximumVideoConferenceUsers is the maximum number of users the service provider supports
     for each video conference call.
    #
    MaximumVideoConferenceUsers=20
  4. Change the values for the MaximumVideoConferenceUsers and MaximumAudioConferenceUsers settings.
  5. Save and close the file.
  6. Restart the server so the change can take effect.
  7. Repeat this process on every Conference Manager. if you have a clustered deployment, apply to every cluster member.