Polycom DOC2702A User Manual
Chapter 4-Additional Conferencing Information
Polycom, Inc.
4-23
—
YES - only the designated Lecturer can be the Content Token holder.
•
The Exclusive Content Mode check box replaces the EXCLUSIVE_CONTENT_ MODE
System Flag which was used to control Exclusive Content Mode for the system in previous
versions.
•
In Exclusive Content Mode, if an endpoint attempts to send Content a few seconds after
another endpoint sent Content, the Content stream it is receiving is momentarily
interrupted by a slide which is displayed for a few seconds before the normal Content
stream is resumed.
Stopping a Content Session
In some cases, when one participant ends the Content session from his/her endpoint, the
Content token is not released and other participants cannot send Content.
The RMX User can withdraw the Content token from the current holder and to return it to
The RMX User can withdraw the Content token from the current holder and to return it to
the MCU for assignment to other endpoints.
To end the current Content session:
>> In the Conferences list pane, right-click the conference icon and then click Abort H.239
To end the current Content session:
>> In the Conferences list pane, right-click the conference icon and then click Abort H.239
Session.
Content Broadcast Control
Content Broadcast Control prevents the accidental interruption or termination of H.239
Content that is being shared in a conference.
Content Broadcast Control achieves this by giving Content Token ownership to a specific
Content Broadcast Control achieves this by giving Content Token ownership to a specific
endpoint via the RMX Web Client. Other endpoints are not able to send content until Content
Token ownership has been transferred to another endpoint via the RMX Web Client.
Guidelines
•
Guidelines
•
Content Broadcast Control is supported in MPM+ and MPMx card configuration modes.
•
Content Broadcast Control is supported in CP and Video Switching conferences.
•
Content Broadcast Control is supported in H.323 environments.
•
Only the selected Content Token owner may send content and Content Token requests
from other endpoints are rejected.
•
Content Token ownership is valid until:
—
—
It is canceled by the RMX User via the RMX Web Client.
—
The owner releases it.
—
The endpoint of the Content Token owner disconnects from the conference.
•
The RMX User can cancel Content Token ownership.