Filter
Top Products
Chapter 3-Additional Conferencing Information
Polycom, Inc. 3-19
2 Select Cancel Content Token Owner in the drop-down menu.
Content Token ownership is cancelled for the endpoint.
Managing Noisy Content Connections
The system can identify participants who send frequent requests to refresh their Content
display usually as a result of a problematic network connection. The frequent refresh
requests cause frequent refresh of the Content display and degrade the viewing quality.
When the system identifies the noisy participants, the system will automatically suspend
the requests to refresh the sent Content to avoid affecting the quality of the Content viewed
by other conference participants. This process is controlled by System flags.
Content Display Flags
• MAX_INTRA_REQUESTS_PER_INTERVAL_CONTENT
Enter the maximum number of refresh (intra) requests for the Content channel sent by
the participant’s endpoint in a 10 seconds interval that will be dealt by the
Collaboration Server system. When this number is exceeded, the Content sent by this
participant will be identified as noisy and his/her requests to refresh the Content
display will be suspended.
Default setting: 3
• MAX_INTRA_SUPPRESSION_DURATION_IN_SECONDS_CONTENT
Enter the duration in seconds to ignore the participant’s requests to refresh the Content
display.
Default setting: 10
• CONTENT_SPEAKER_INTRA_SUPPRESSION_IN_SECONDS
This flag controls the requests to refresh (intra) the Content sent from the Collaboration
Server system to the Content sender as a result of refresh requests initiated by other
conference participants.
Enter the interval in seconds between the Intra requests sent from the Collaboration
Server to the endpoint sending the Content to refresh the Content display. Refresh
requests that will be received from endpoints within the defined interval will be
postponed to the next interval.
Default setting: 5
Forcing Other Content Capabilities
•The H239_FORCE_CAPABILITIES System Flag in system.cfg gives additional control
over Content sharing:
— When the flag is set to NO (default), the Collaboration Server only verifies that the
endpoint supports the content protocols: H.263 or H.264.
— When set to YES, the Collaboration Server checks frame rate, bit rate, resolution,
annexes and all other parameters of the Content mode as declared by an endpoint
during the capabilities negotiation phase. If the endpoint does not support the
Content capabilities of the MCU, the participant will not be able to send or receive
content over a dedicated content channel.