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
•
•
•
•
•
•
•
Giving and Cancelling Token Ownership
To give token ownership:
1
2
Polycom, Inc.
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 an administrator, operator or chairperson using the
RMX Web Client.
— The owner releases it.
— The endpoint of the Content Token owner disconnects from the conference.
An administrator, operator or chairperson can cancel Content Token ownership.
In cascaded conferences, a participant functioning as the cascade link cannot be given
token ownership.
In the Participants list, right click the endpoint that is to receive Content Token
ownership.
Select Change To Content Token Owner in the drop-down menu.
The endpoint receives ownership of the Content Token and an indication icon is
displayed in the Role column of the participant's entry in the Participants list.
Chapter 2-Additional Conferencing Information
2-77