Sharing Content During Conferences
Polycom®, Inc. 138
Forcing Other Content Capabilities
The H239_FORCE_CAPABILITIES system flag allows additional control of content sharing:
● When set to NO (default) - The MCU merely verifies the endpoint supports the content protocols:
H.263 or H.264.
● When set to YES - The MCU verifies frame rate, bit rate, resolution, annexes, and all other
parameters of content as declared by an endpoint during the capabilities negotiation phase. If the
endpoint does not support the content capabilities of the MCU, the participant cannot share content
over a dedicated content channel.
Managing Noisy Content Connections
The system can identify participants sending frequent content display refresh requests (usually as a result
of a problematic network connection), which cause frequent refreshing of content display, and degrading of
viewing quality.
When the system identifies such “noisy” participants, it marks them (in the Conference Participants list,
Status column) as Noisy, and automatically suspends these requests to avoid affecting the quality of the
content viewed by the other conference participants.
This process is controlled by the following system flags:
● MAX_INTRA_REQUESTS_PER_INTERVAL_CONTENT -
The maximum number of refresh (intra) requests per 10-second intervals allowed for an endpoint.
Beyond that number, content sent by this participant is identified as “noisy”, and its refresh requests
are suspended.
Default setting: 3
● MAX_INTRA_SUPPRESSION_DURATION_IN_SECONDS_CONTENT -
The duration, in seconds, for ignoring the participant’s content display refresh requests.
Default setting: 10
● CONTENT_SPEAKER_INTRA_SUPPRESSION_IN_SECONDS -
The interval, in seconds, between content refresh (intra) requests sent from the MCU to the content
sender due to refresh requests initiated by other conference participants. Additional refresh requests
received within that interval are deferred to the next interval.
Default setting: 5
To Next Page
Loading...
