Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Managing conferences
Cisco TelePresence MCU 4.3 Product administration guide
Page 54 of 242
participant, and if the auto attendant connection "borrows" the last remaining media port, then that connection
will be dropped if another endpoint connects directly to a conference and requires a reserved media port.
will be dropped if another endpoint connects directly to a conference and requires a reserved media port.
Changing MCU port reservation mode
In general, changing port reservation mode when there are active connections is not recommended. The
effects of changing mode include, but are not necessarily limited to:
effects of changing mode include, but are not necessarily limited to:
n
Destruction of ad hoc conferences
Any ad hoc conferences in progress will be destroyed when changing to port reservation mode and their
participants dropped because
Any ad hoc conferences in progress will be destroyed when changing to port reservation mode and their
participants dropped because
are not permitted in port reservation mode.
n
Participant disconnection
Participants in a scheduled conference may be disconnected. For each conference, the maximum port
usage values (for unreserved mode) and the ports to reserve (for reserved mode) are configured and stored
separately. Therefore when changing port reservation mode, it is possible that there are more active
participants than allowed in the particular mode. In this case, participants are disconnected to reduce the
number to that allowed.
Participants in a scheduled conference may be disconnected. For each conference, the maximum port
usage values (for unreserved mode) and the ports to reserve (for reserved mode) are configured and stored
separately. Therefore when changing port reservation mode, it is possible that there are more active
participants than allowed in the particular mode. In this case, participants are disconnected to reduce the
number to that allowed.
Content channel video support
The MCU supports an additional video channel known as the content channel for each conference. This
feature encompasses:
feature encompasses:
n
H.239 video streams sent from the MCU to viewing H.323 endpoints
n
Sourcing the content channel from a H.323 endpoint's H.239 video stream, a SIP endpoint supporting
content using BFCP , or a VNC connection
content using BFCP , or a VNC connection
n
Streaming the content channel to users' desktop machines as a pane in the conference view
n
Streaming the content channel to users' desktop machines as a separate window (where markup and text
chat can also be used)
chat can also be used)
(*)
n
Showing the content as part of the main video channel, where an endpoint cannot, for whatever reason,
receive the content channel as an additional video channel. That is, the participant will see the content as a
pane in the conference layout
receive the content channel as an additional video channel. That is, the participant will see the content as a
pane in the conference layout
n
Content
n
Allowing graphical and textual "markup" of the content channel
(*)
n
Text chat between conference participants
(*)
* - these features require the
web conferencing feature key
.
Content channel vs. main video
The H.239 protocol allows the MCU to support an additional video stream to or from each connected
endpoint. Therefore, there are potentially three media streams between each endpoint and the MCU: audio,
main video and content video.
endpoint. Therefore, there are potentially three media streams between each endpoint and the MCU: audio,
main video and content video.
The main video is the normal multi-pane conference view showing participants' video streams composed
within the selected layout. The differences between the content channel video and the main video are:
within the selected layout. The differences between the content channel video and the main video are:
n
Single layout
Each participant in a conference can normally select their own individual main video layout (e.g. a 2 x 2 grid
of other participants, one large focused pane plus eight smaller panes) and they are free to change this
layout as many times as desired while they are connected to the conference.
By comparison the content channel video always shows just a single video stream, "full screen", and each
Each participant in a conference can normally select their own individual main video layout (e.g. a 2 x 2 grid
of other participants, one large focused pane plus eight smaller panes) and they are free to change this
layout as many times as desired while they are connected to the conference.
By comparison the content channel video always shows just a single video stream, "full screen", and each