Filter
Top Products
RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Administrator’s Guide
Polycom®, Inc. 173
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 Collaboration Server 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 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 endpoint via the
Collaboration Server Web Client. Other endpoints are not able to send content until Content Token
ownership has been transferred to another endpoint via the Collaboration Server Web Client.
Guidelines for Controlling Content Broadcast
● 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 Collaboration Server User via the Collaboration Server Web Client.
The owner releases it.
The endpoint of the Content Token owner disconnects from the conference.
● The Collaboration Server User can cancel Content Token ownership.
● In cascaded conferences, a participant functioning as the cascade link cannot be given token
ownership.