Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Content channel video support
Cisco TelePresence MCU Version 4.2 Printable online help
Page 62 of 252
VNC connection
A VNC connection is one where the MCU has made a connection to a remote device (normally a
desktop PC) and is receiving a video stream from that device; this is typically used for including a
slide-based presentation in a conference.
A VNC connection is one where the MCU has made a connection to a remote device (normally a
desktop PC) and is receiving a video stream from that device; this is typically used for including a
slide-based presentation in a conference.
If Automatic content handling is disabled, and a conference is configured with content channel
support, when a VNC "participant" is added to that conference, the MCU will attempt to use the
VNC video as the content channel. This is normally the desired behavior; however, there are a
couple of caveats:
support, when a VNC "participant" is added to that conference, the MCU will attempt to use the
VNC video as the content channel. This is normally the desired behavior; however, there are a
couple of caveats:
•
If there is a video conferencing endpoint actively contributing content video then it will not be
possible to immediately switch over to using the VNC video instead - the switch over will
occur when the participant closes his content channel.
possible to immediately switch over to using the VNC video instead - the switch over will
occur when the participant closes his content channel.
•
With more than one active VNC connection in a conference, the first will be used as the
content channel source, and subsequent connections will be shown in main video layout
panes, just as if the conference had no content channel facility. If the currently active VNC
connection is either disconnected or its use as the content channel disabled, another VNC
video stream will start to be used as the content channel.
content channel source, and subsequent connections will be shown in main video layout
panes, just as if the conference had no content channel facility. If the currently active VNC
connection is either disconnected or its use as the content channel disabled, another VNC
video stream will start to be used as the content channel.
If Automatic content handling is enabled:
•
If there is a video conferencing endpoint actively contributing content video, the MCU will
automatically switch to using the VNC video as the content channel.
automatically switch to using the VNC video as the content channel.
•
If there is already an active VNC connection in a conference, a second VNC connection will
automatically replace the first as the content channel (rather than appearing as a pane in the
main video).
automatically replace the first as the content channel (rather than appearing as a pane in the
main video).
Participant main video
It is also possible for the MCU to use a endpoint's main video channel as the conference's content
channel. This has the same caveats as the use of a
It is also possible for the MCU to use a endpoint's main video channel as the conference's content
channel. This has the same caveats as the use of a
VNC connection
for the content channel, as
described above.
Video markup
Whichever of the content channel sources mentioned above is active, the MCU provides the
facility for users to add markup to the video channel. This markup consists of an additional video
overlay on to which graphics may be drawn and text added; content channel viewers see the
content channel source video plus this overlay. The overlay can be cleared later leaving the
source video unaltered.
Whichever of the content channel sources mentioned above is active, the MCU provides the
facility for users to add markup to the video channel. This markup consists of an additional video
overlay on to which graphics may be drawn and text added; content channel viewers see the
content channel source video plus this overlay. The overlay can be cleared later leaving the
source video unaltered.
MCU content channel configuration
Unit-wide or Blade-wide configuration
At the unit-wide/blade-wide level, the MCU can be configured to disallow the use of conference
content channels completely. If the content channel facility is enabled, the MCU can be separately
configured not to allow textual or graphical markup of the content, and whether to make text chat
visible to connected endpoints.
content channels completely. If the content channel facility is enabled, the MCU can be separately
configured not to allow textual or graphical markup of the content, and whether to make text chat
visible to connected endpoints.
You can choose to enable encryption on the MCU. When encryption is used, the content channel will
be encrypted.
be encrypted.
For more information on these configuration parameters, see
Per-conference configuration
Assuming that content is enabled on the MCU unit-wide/blade-wide, each scheduled conference can
be independently configured to allow content channel operations or not. If enabled, this has an impact
on the conference's
be independently configured to allow content channel operations or not. If enabled, this has an impact
on the conference's
port usage
; if disabled, then all attempts by participants in that conference to open
a content channel to the MCU will be unsuccessful.