Operations Performed During On Going Conferences; Conference Level Operations; Changing The Duration Of A Conference - Polycom Collaboration Server (RMX) 1500 Deployment Manual

Table 2-6
Column
Audio
Video
Encryption
FECC Token
Content Token
For more information, see the RealPresence Collaboration Server (RMX) 1500/2000/4000
Administrator's Guide for Maximum Security Environments, "Participant Level Monitoring" on
page 8-10.

Operations Performed During On Going Conferences

Conference Level operations

Changing the Duration of a Conference

The duration of each conference is set when the new conference is created. The default
duration of a conference is 1 hour. All conferences running on the RMX are automatically
extended as long as there are participants connected to the conference.
Polycom, Inc.
Participant Monitoring – Indicators and Properties (Continued)
Icon/Description
Displays the status of the participant's audio channel.
If the participant's audio is connected and the channel is neither muted nor
blocked, no indication is displayed.
Muted – Participant's audio channel is muted. The participant can still
hear the conference.
Blocked – Transmission of audio from the conference to the participant
is blocked.
Muted and Blocked - Audio channel is muted and blocked.
Displays the status of the participant's video channel.
If there is no problem with the participant's video connection and the channel is
neither suspended nor secondary, no indication is displayed.
Suspended – Video transmission from the endpoint to the conference is
suspended.
Secondary – Participant is connected only through the audio channel
due to problems with the video channel.
Indicates that the endpoint is connected to the conference using
encryption.
Participant is the holder of the FECC token and has Far End Camera
Control capabilities.
The FECC token can be allocated to only one participant at a time and
remains un-allocated if no participant requests it.
Participant is the holder of the Content token and has content sharing
permission.
The Content token can be allocated to only one participant at a time and
remains un-allocated if no participant requests it.
For more information, see the RealPresence Collaboration Server
(RMX) 1500/2000/4000 Administrator's Guide for Maximum Security
Environments, "H.239" on page 2-12.
Chapter 2-Basic Operation
2-33