Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Configuring content settings
Cisco TelePresence MCU Version 4.2 Printable online help
Page 171 of 252
Configuring content settings
The content settings affect the behavior of the MCU with regard to H.239 and BFCP (Binary Floor
Control Protocol).
Control Protocol).
H.239 is the protocol that allows for an additional video channel (known as the content channel)
alongside the main video channel in a video-conferencing call that uses H.323; BFCP is a protocol
that allows for an additional video channel (known as the content channel) alongside the main video
channel in a video-conferencing call that uses SIP.
alongside the main video channel in a video-conferencing call that uses H.323; BFCP is a protocol
that allows for an additional video channel (known as the content channel) alongside the main video
channel in a video-conferencing call that uses SIP.
For example, a conference participant may want to contribute a slide presentation from a laptop within
a video conference.
a video conference.
For more information about content support in conferences, refer to
To access these settings, choose Settings > Content.
Refer to this table for assistance configuring the content settings. After making any configuration
changes, click Apply changes.
changes, click Apply changes.
Field
Field description
Usage tips
Content
status
status
Controls whether the MCU as a whole is
permitted to use content.
permitted to use content.
If this setting is Enabled, you can still
enable or disable the use of content on a
per-conference basis. For more information
about configuring individual conferences,
refer to
enable or disable the use of content on a
per-conference basis. For more information
about configuring individual conferences,
refer to
If this setting is Disabled, no conference
will be able to use content.
will be able to use content.
If this setting is H.239 only, no conference
will be able to use BFCP content.
will be able to use BFCP content.
Certain video conferencing endpoints and
infrastructure such as gatekeepers may not
operate correctly when communicating with
equipment (such as the MCU) which
declares H.239 capability. It may therefore
be necessary to set this to Disabled in
order to work with legacy devices (this will,
of course, also prevent content video
streams being used with any H.239- or
BFCP-aware equipment).
infrastructure such as gatekeepers may not
operate correctly when communicating with
equipment (such as the MCU) which
declares H.239 capability. It may therefore
be necessary to set this to Disabled in
order to work with legacy devices (this will,
of course, also prevent content video
streams being used with any H.239- or
BFCP-aware equipment).