Cisco Cisco TelePresence MCU 4510 Release Notes
New features in 4.4
Cisco TelePresence MCU 4.4(3.54) Maintenance Release Notes
Page 5 of 27
Video to use by default
You can now configure a participant to display a different participant's video source by default.
The MCU shows the replacement video by default whenever the original participant's video would previously
have been shown. For example, if the original participant becomes the active speaker, then by default the
replacement video becomes the most prominent pane in the layout.
have been shown. For example, if the original participant becomes the active speaker, then by default the
replacement video becomes the most prominent pane in the layout.
The original participant's video never shows in the conference while the replacement video is available,
unless you explicitly choose to show the original participant's video in a specified pane in the layout.
unless you explicitly choose to show the original participant's video in a specified pane in the layout.
This replacement is only effective when both participants are in the conference. If the video to use by default
is not available, the MCU tries to use the original participant's video.
is not available, the MCU tries to use the original participant's video.
The configuration is applied only on the participant whose video will be replaced: no changes are required to
the source participant's configuration. The source participant does not see the replacement video by default -
that is, they won't see themself when their video is replacing another participant and they would otherwise
have seen that participant. Multiple participants can use the same video to use by default setting.
the source participant's configuration. The source participant does not see the replacement video by default -
that is, they won't see themself when their video is replacing another participant and they would otherwise
have seen that participant. Multiple participants can use the same video to use by default setting.
Adaptive Gain Control (AGC) on join
You can now apply adaptive gain control (AGC) to templates, conferences or participants in advance so that
the gain is automatically controlled when participants join conferences.
the gain is automatically controlled when participants join conferences.
AGC means that the participant's audio levels are adjusted to a common reference level to ensure a
consistent audio experience for all participants.
consistent audio experience for all participants.
A participant's AGC setting always overrides a setting inherited from the conference settings, and automatic
gain will be disabled for a connected participant when you manually change the gain.
gain will be disabled for a connected participant when you manually change the gain.
Mute outgoing audio or stop outgoing video
The MCU can be configured to mute the audio or stop the video sent to a particular participant. The MCU now
also signals all muting, with the exception of incoming audio. This exception is made by design, to ensure
DTMF functionality which may otherwise have been impaired in some cases.
also signals all muting, with the exception of incoming audio. This exception is made by design, to ensure
DTMF functionality which may otherwise have been impaired in some cases.
Suppress audio during DTMF
The MCU now has an option to suppress the audio coming from an endpoint when the MCU is sending the
connection DTMF sequence to the endpoint, so that other participants do not hear the audio from the
endpoint while it is connecting.
connection DTMF sequence to the endpoint, so that other participants do not hear the audio from the
endpoint while it is connecting.
The audio suppression continues until the whole DTMF sequence is complete, even if the sequence contains
leading or trailing commas - which create pauses of two seconds each.
leading or trailing commas - which create pauses of two seconds each.
This suppression is independent of other audio muting options and also persists during retries. This is
necessary in combination with the persistence feature because, if the MCU needs to redial an endpoint in the
middle of the conference, the other participants should not hear the audio from the endpoint while it is
connecting.
necessary in combination with the persistence feature because, if the MCU needs to redial an endpoint in the
middle of the conference, the other participants should not hear the audio from the endpoint while it is
connecting.
The option can be applied to ad hoc participants and preconfigured endpoints.
Note: the maximum length of the DTMF sequence has been extended to 127 characters. In prior versions
there was a 31 character limit.
there was a 31 character limit.