19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 3-Additional Conferencing Information<br />

Content Broadcast Control achieves this by giving Content Token ownership to a specific<br />

endpoint via the <strong>RMX</strong> Web Client. Other endpoints are not able to send content until Content<br />

Token ownership has been transferred to another endpoint via the <strong>RMX</strong> Web Client.<br />

<strong>Guide</strong>lines<br />

• Content Broadcast Control is supported in MPM+ and MPMx card configuration modes.<br />

• Content Broadcast Control is supported in CP and Video Switching conferences.<br />

• Content Broadcast Control is supported in H.323 environments.<br />

• Only the selected Content Token owner may send content and Content Token requests<br />

from other endpoints are rejected.<br />

• Content Token ownership is valid until:<br />

— It is canceled by an administrator, operator or chairperson using the<br />

<strong>RMX</strong> Web Client.<br />

— The owner releases it.<br />

— The endpoint of the Content Token owner disconnects from the conference.<br />

• An administrator, operator or chairperson can cancel Content Token ownership.<br />

• In cascaded conferences, a participant functioning as the cascade link cannot be given<br />

token ownership.<br />

Giving and Cancelling Token Ownership<br />

To give token ownership:<br />

1 In the Participants list, right click the endpoint that is to receive Content Token<br />

ownership.<br />

2 Select Change To Content Token Owner in the drop-down menu.<br />

The endpoint receives ownership of the Content Token and an indication icon is<br />

displayed in the Role column of the participant’s entry in the Participants list.<br />

<strong>Polycom</strong>, Inc. 3-55

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!