Configuring global conference settings

Choose the MCU-wide setting for motion/sharpness trade off. The options are:

• Favor motion: the MCU will try and use a high frame rate. That is, the MCU will strongly favor a resolution of at least 25 frames per second
• Favor sharpness: the MCU will use the highest resolution that is appropriate for what is being viewed
• Balanced: the MCU will select settings that balance resolution and frame rate (where the frame rate will not be less than 12 frames per second)

The settings for motion (frames per second) and sharpness (frame size or resolution) are negotiated between the endpoint and the MCU. This setting controls how the MCU will negotiate the settings to be used with an endpoint.

Note that the Motion/sharpness trade off setting for an individual endpoint will override this global conference setting during calls with that endpoint.

Choose the global conference setting for transmitted video resolutions. This setting can be overridden by individual configured endpoint settings.

Retain the default setting (Allow all resolutions) unless you are experiencing problems with the display of certain resolutions by endpoints.

Endpoints advertise the resolutions that they are able to display. The MCU then chooses from those advertised resolutions, the resolution that it will use to transmit video. However, some endpoints do not display widescreen resolutions optimally. In these cases, you might want to use this setting to restrict the resolutions available to the MCU.

Note that you can configure this setting for individual configured endpoints if you do not need to restrict transmitted video resolutions for all endpoints.

Identifies the network capacity (measured in bits per second) used by the media channels established by the MCU to a single participant.

When the MCU makes a call to an endpoint, the MCU chooses the maximum bandwidth that is allowed to be used for the media channels which comprise that call. This field sets that maximum bandwidth, and is the total bandwidth of the audio, video, and content channels combined.

This setting can be overridden by individual endpoints' Preferred bandwidth from MCU values.

Sets the bandwidth that the MCU will advertise to the endpoint when it calls it.

This setting can be overridden by individual endpoints' Preferred bandwidth to MCU values.

Determines which layout views (see Customizing layout views) new participants see when connecting to conferences.

Regardless of the family chosen here, participants can cycle through the available families using the far-end camera controls. See Understanding how participants display in layout views.

When there are only two participants, each participant will see the other in full-screen view.

If selected, when there are only two participants in a conference, this will apply regardless of which layout was originally chosen for the conference. If you do not select this setting, then the default family view is used with unused panes blank.

When in a conference, there is generally one participant that the MCU recognizes as the active speaker, notionally the person currently speaking the loudest. This setting determines how the MCU displays that participant in conference views.

• None
  With this setting, no special action is taken when displaying the active speaker.
• Red border
  Displays a red border around the active speaker.
• Green border
  Displays a green border around the active speaker.

Specifically, an active speaker is the participant who has been identified by the MCU as the current loudest speaker, and they are currently speaking. When you choose to have a border display around the active speaker, it will only display when that participant is speaking.

Determines whether the MCU is operating in Reserved mode (Media port reservation Enabled) or Unreserved mode (Media port reservation Disabled).

Note that if you set this field to Enabled, you will not be able to create ad hoc conferences. See Port reservation modes for additional information.

Allows various audible in-conference features to be enabled or disabled.

The options are:

• Conference timing: audible messages to indicate when the conference's scheduled end time is approaching.
• Join and leave indications: audible messages indicating when other participants join and leave the conference.
• Conference status: audible status messages for example indicating to a participant that he is the only participant in a conference.

Allows various in-conference icons to be displayed on participants' endpoints.

Depending on the check boxes that are selected, in-conference icons appear:

• Important participant: a crown icon appears on all participants' endpoints in the pane of the participant that has become important.

• Unsecured conferences: encrypted participants in a conference where encryption is optional see an icon indicating that there are other participants who are unencrypted.

• Tunneled camera control: an arrow icon appears on their endpoint when one participant uses the far-end camera control to control another's camera.
• Layout changes: an icon appears on their endpoint when a participant changes their layout view.
• Recording indicator: an icon (a red dot) appears near the top left of the conference display to indicate that the conference is being recorded. For the recording indicator to display, the recording must be made by an IP VCR running software version 2.1 or later, and the connection between the IP VCR and the MCU must be using H.323.
• Audio participants: an icon appears near the top left of the conference display to indicate if there are any audio-only participants. To the right of the icon, the number of such participants will be displayed. If enabled, the icon will only display if there are one or more audio participants.
  Audio-only participants are participants that cannot be viewed; either the participant's endpoint cannot send video, the MCU has not allocated a video port to the participant, the participant has stopped their video, or the MCU has stopped the video received from the endpoint.
• Media quality: an icon (video camera with a cross through it) appears when a participant is experiencing high packet loss or if the network link's bandwidth is too low for the type of channel to the MCU that the endpoint has established.

Refer to Using in-conference features with video endpoints to see all in-conference icons and their descriptions.

Allow various in-conference features to be enabled or disabled.

Depending on the check boxes that are selected, in-conference messages appear:

• Conference status: messages appear when the conference's scheduled end time is approaching and when other participants join and leave the conference. Status messages can also be played for example when you are the only participant in a conference
• Conference timing: a message appears when the conference's scheduled end time is approaching
• Join and leave indications: messages appear when other participants join and leave the conference
• Text messages: allows a message sent using the web interface to be displayed on participants' endpoints
• Content channel text chat: messages that users can send one another via the content channel are displayed on participants' endpoints. Note that this functionality is only available if the web conferencing option (WCO) is activated on your MCU.

This setting controls for how long (if at all) the Cisco logo is displayed to participants joining a conference. When displayed, the logo appears in the bottom right of a participant's conference display. Choose from:

• <never show>
• 5 seconds
• 10 seconds
• 1 minute
• <permanent>

Allows you to enter a message that will be seen by participants joining conferences on the MCU. The message is displayed at the bottom of a participant's conference display.

The duration of the message is configured using the Conference welcome message duration control.

This setting controls for how long (if at all) participants joining a conference will see the conference welcome message. Choose from:

• <never show>
• 5 seconds
• 10 seconds
• 1 minute
• <permanent>

This setting controls whether (and for how long) participants shown in view panes are accompanied by their supplied name.

The "Conference welcome message" (described above) and any other overlaid textual messages (for instance information on how soon the conference is going to end, or endpoints leaving and joining the conference) will take priority over the displaying of participant names for the duration of those messages.

Restricts the MCU's choice of audio codecs to be used for transmitting audio to endpoints.

When communicating with an endpoint, the MCU receives a list of supported audio codecs from the endpoint. The MCU chooses an audio codec from those available, and sends audio data to the endpoint in that format.

Note that the Custom codec selection setting for an individual endpoint will override this global conference setting for calls to that endpoint.

Determines which audio codecs the MCU advertises to remote endpoints, restricting the endpoints' choice of channels available for sending audio data to the MCU.

Note that the Custom codec selection setting for an individual endpoint will override this global conference setting for calls from that endpoint.

Restricts the MCU's choice of video codecs to be used for transmitting main video (not content) to endpoints.

This setting only affects main video, not content. The outgoing transcoded content video codec can be selected on a per conference basis. Click here for more information. The outgoing passthrough content video codec cannot be selected. The MCU always advertises support for both H.263+ and H.264.

When communicating with an endpoint, the MCU receives a list of supported video codecs from the endpoint. The MCU chooses a video codec from those available, and sends video data to the endpoint in that format.

Note that the Custom codec selection setting for an individual endpoint will override this global conference setting for calls to that endpoint.

Determines which video codecs the MCU advertises to remote endpoints, restricting the endpoints' choice of channels available for sending main video data (not content) to the MCU.

This setting only affects main video, not content. The incoming content video codec cannot be selected. The MCU always advertises support for both H.263+ and H.264.

Note that the Custom codec selection setting for an individual endpoint will override this global conference setting for calls from that endpoint.

When enabled, the MCU will upscale video streams from participants who are sending low resolution video with the purpose of making best use of the MCU's HD video capabilities.

The MCU uses intelligent resolution upscaling technology to improve the clarity of low-resolution video. Select this setting to enable it to do so.

ClearVision is not available if your MCU is running in Standard definition mode. To configure media port modes, go to Settings > Media ports.

Allows the MCU to vary the resolution and codec of the video being sent to a remote endpoint within the video channel established to that endpoint. The options are:

• None: Do not allow video size to be changed during transmission
• Dynamic resolution only: Allow video size to be optimized during transmission
• Dynamic codec and resolution: Allow video size to be optimized during transmission and/or dynamic codec selection

With this option enabled, the MCU can, for instance, decide to send CIF video within a 4CIF channel if this will increase the viewed video quality.

The circumstances under which decreasing the video resolution can improve the video quality include:

• if the original size of the viewed video is smaller than the outgoing channel
• if the remote endpoint has used flow control commands to reduce the bandwidth of the MCU video transmission

Typically, lowering the resolution means that the MCU can transmit video at a higher frame-rate.

This setting can be used to influence the choice of outgoing video resolution made by the MCU in certain circumstances.

• Default
  The MCU will use its normal internal algorithms to dynamically decide which resolution to send in order to maximize the received video quality.
• Favor 448p
  The MCU will heavily favor sending 448p or w448p video (resolutions of 576 x 448 and 768 x 448 pixels respectively) to those endpoints that are known to work best with these resolutions.

You should leave this at Default unless your environment dictates 448p or w448p resolutions only.

Sets the format for video transmitted by the MCU.

• NTSC
  The MCU will transmit video at 30 frames per second (or a fraction or multiple of 30, for example: 15fps or 60fps)
• PAL
  The MCU will transmit video at 25 frames per second (or a fraction or multiple of 25, for example: 12.5fps or 50fps)

This option should be set to match your endpoints' video configuration. If you set this incorrectly, the smoothness of the video both to and from the endpoints might suffer.

NTSC is typically used in North America, while PAL is typically used in the UK and Europe.

Sets the maximum payload size (in bytes) of the packets sent by the MCU for outgoing video streams (from the MCU to connected video endpoints).

We recommend that you use the default setting (1400 bytes) wherever possible. If you need to reduce the maximum payload size, we recommend a value of at least 1000 bytes; a maximum payload size that is too low reduces the overall bandwidth efficiency and may impact performance.

Video streams generally contain packets of different lengths. This parameter only sets the maximum size of a transmitted network datagram. The MCU optimally splits the video stream into packets of this size or smaller. Thus, most transmitted packets will not reach this maximum size.

Controls whether the MCU restricts video resolutions in order to reduce the effect of interlacing artifacts.

You should only enable this option if you are seeing video interlacing artifacts or on the advice of Customer support. Note that all resolution restrictions imposed by this setting apply only to video being sent from endpoints to the MCU.

Enables the MCU to send bandwidth control messages to optimize the video bandwidth being used.

The MCU can send these messages to endpoints requesting that the bandwidth of the video that they are sending be decreased or increased, up to the maximum bandwidth of the channel.

If the participant is very prominent, then the MCU will ask the endpoint to send video at a high bandwidth. If the participant is not being viewed at all (or only being viewed in very small view panes), the MCU will request that the video is sent at a lower rate to conserve network bandwidth.

Enables the MCU to request that the endpoint send lower speed video if it fails to receive all the packets which comprise the far end's video stream.

The MCU can send these messages to endpoints requesting that the bandwidth of the video that they are sending be decreased based on the quality of video received by the MCU.

If there is a bandwidth limitation in the path between the endpoint and the MCU, it is better for the MCU to receive every packet of a lower rate stream than to miss some packets of a higher rate stream.

Prevents the MCU from showing conference participants their own video in small panes of variable-sized pane views (and in conferences with equal-sized panes).

If this option is set, then a participant will never appear in a small pane (self-view), even if there is a free small pane available. They may still appear in larger panes, however, for example if the view focus is manually changed to show their video. See Understanding how participants display in layout views for more details.

Prevents the MCU from duplicating large-pane participants in small panes.

When using a conference view with some large and some small panes, the MCU will typically duplicate in a small pane the video of a participant shown in a large pane. This is done to minimize the switching of small panes in response to changes of participant focus in the large pane. If you would prefer not to duplicate participants in small panes in this way, select this option. For more details of view layouts, see Understanding how participants display in layout views.

Any new content channel in a conference will be treated as important and displayed prominently to all participants who see the content channel in their conference layout.

When this setting is enabled, any endpoint successfully contributing content to a conference is immediately treated as important. This has the same affect as using the 'crown' icon in the content channel row of a conference's Participant list page.

An administrator can remove the importance from the content channel at any time in the conference.

This setting does not affect participants who view the content channel independently from their conference panes (for example, those viewing the content channel on a separate video screen).

This setting will not affect those participants using pane placement. Participants using pane placement who have not allocated a pane to the content channel, will not see the content channel even if it is 'important'.

When pane placement is in use, this option affects the potential duplication of participants that are specifically placed in view panes with view panes configured to show the conference's current active speaker.

• Never duplicate placed participants
  A pane set to show the loudest speaker will never show a participant that is specifically configured to be displayed in another layout pane. If another layout pane has been configured to show the participant which is the current active speaker, panes set to show the loudest speaker will instead show the conference's previous loudest speaker.
  If you never want a pane that is set to <loudest speaker> to duplicate a participant shown in another layout pane, choose this setting.
• Allow duplication of placed participants in small panes only
  This is the default setting; panes configured to show the loudest speaker will be able to show participants that are configured to be displayed in one or more small panes for that layout, but not those shown in big panes. This is most appropriate when using layouts with more than one big pane, in order to make best use of the screen area.
• Allow duplication of placed participants in any pane
  Panes set to <loudest speaker> will always show the current active speaker for a conference, whether or not any other layout panes have been specifically configured to show that participant.

For more details of view layouts, see Understanding how participants display in layout views.

When pane placement is in use, this option determines how often panes set to "rolling" change which participant they are showing.

For more details of view layouts, see Understanding how participants display in layout views. and Using pane placement.

Defines the maximum height of the participant's name as a percentage of the pane height.

Enter a percentage value. e.g. 20 will prevent the text from taking more than 20% of the pane height. The setting is particular to small panes; it does not scale the text beyond the text's own maximum size.

Determines how easy it is for a participant to replace the active speaker for a conference based on how loudly they are speaking.

A value of 0 means that it is very difficult for the active speaker to be replaced; a value of 100 means the active speaker can be replaced very easily.

Sets the default action when endpoints call into the MCU using an unknown E.164 number, conference number, or auto attendant. In other words, a number that does not correspond to any configured conference.

• Default auto attendant
  The endpoint will enter the default auto attendant from which they may join existing conferences or potentially create a new conference (see Using an auto attendant). This behavior is the same as if the endpoint had called the MCU using its IP address rather than a number.
• Disconnect caller
  Endpoints are not allowed to call unknown conference or auto attendant numbers, and the call will be terminated.
• Create new ad hoc conference
  A new conference will be created with the number called as its numeric identifier. The endpoint automatically joins this new conference. This option is not available if the MCU is in port reservation mode.

This option can make it easier for callers to create ad hoc conferences if Create new ad hoc conference is selected. If you do not want callers to be able to create conferences in this way, select one of the other options.

Defines whether and how the MCU will redial preconfigured endpoints if the connection fails:

• Never redial
  The MCU never attempts to redial a failed connection to a preconfigured participant.
• Redial until connected
  The MCU redials the preconfigured participant if it fails unexpectedly when first establishing a connection; the MCU never retries the connection if it fails after being established.

• Redial on unexpected disconnection
  The MCU redials preconfigured participants on any unexpected disconnection, whether it occurs while first being established or at any point thereafter. It does not attempt to redial if the participant deliberately ends the connection.

  Note: A deliberate disconnection, if it is not correctly signaled by the endpoint, may be interpreted as unexpected. If you experience this, reduce the call persistence behavior for the affected endpoint.

• Redial on any disconnection
  The MCU redials the preconfigured participant when the connection closes, irrespective of whether the call fails or is deliberately ended by the participant.

This setting defines the box-wide behavior for conferences dialing preconfigured participants. The setting may be overridden by the corresponding setting on individual preconfigured endpoints.

Although this box-wide setting applies only to preconfigured endpoints, the equivalent option is provided when you are inviting ad hoc participants.

The redial limit allows the MCU to stop trying to reconnect a failed call. When the limit is enabled, the MCU will attempt to reconnect up to ten times: once immediately after the connection failure; four times at one minute intervals thereafter, and once every five minutes for a further five attempts.

When the redial limit is disabled, the MCU continues retrying - once every five minutes - after those first ten attempts. It will do this until the connection is made. If the connection is never made, the MCU continues retrying until either the conference or the participant is destroyed.

The redial pattern has an initial delay when the redial behavior is set to Redial on any disconnection. With that setting, the MCU does not immediately redial after a deliberate disconnection - it waits 30 seconds.

This setting enables or disables the redial limit for all conferences when they are redialing preconfigured participants. The setting may be overridden by the corresponding setting on individual preconfigured or ad hoc endpoints.

When enabled, conferences remain locked when all participants leave the conference.

Without this option selected, when the final participant leaves a locked conference, the MCU unlocks that conference.

If enabled, when the MCU is calling out to an endpoint, the caller ID that the endpoint will see is the conference name.

Without this option selected, the caller ID is the name of the MCU. This setting applies to both H.323 and SIP endpoints.

Instructs the MCU to request conference participants dialing into protected conferences using an E.164 number via an H.323 gatekeeper to enter a PIN before they may join the conference.

You may want participants joining a conference via a gatekeeper not to need to enter a PIN, even for protected conferences. If this is the case, do not set this option. If you want conferences to be protected, regardless of how participants connect, ensure you set this option.

When this option is set, participants calling into a protected conference will be presented with PIN-entry screen instead of the normal conference view. The option has no effect for conferences with no PIN set.

If this option is checked, a participant creating an ad hoc conference must enter a PIN for that conference. The MCU will not create the conference until the participant enters a PIN.

When a PIN is required for ad hoc conferences, the auto attendant will wait forever for the participant to enter a PIN.

This option is required in some highly secure environments.

The minimum number of digits required for a PIN.

This field is only available if Require a PIN for ad hoc conferences is selected. This forces a participant who is creating an ad hoc conference to protect it with a PIN with at least this number of digits.

The timeout setting for a participant entering a PIN for an ad hoc conference that they are currently creating:

• <never configure PIN>
  Participants will never be prompted to enter a PIN when creating an ad hoc conference.
• 10 seconds, 30 seconds, 1 minute
  Participants will be prompted for a PIN when creating an ad hoc conference. If the participant does not enter a PIN during the configured time period, the conference will be created without a PIN.
• <wait forever>
  Participants will be prompted for a PIN when creating an ad hoc conference. They must either enter a PIN to create an ad hoc conference with a PIN or press the hash/pound key (#) to create the conference without a PIN.

This global setting may be useful where participants creating ad hoc conferences rarely need to configure a PIN.

This field is unavailable when Require a PIN for ad hoc conferences is selected. When a PIN is required for ad hoc conferences, the auto attendant will wait forever for the participant to enter a PIN.

If this option is checked, the MCU advertises the ability to receive out of band DTMF.

If this option is checked, endpoints are allowed to send out of band DTMF. If this option is unselected, the MCU will not advertise the ability to accept out of band DTMF and endpoints will instead be forced to use in band DTMF.

Prior to release 4.1, the MCU always advertised to endpoints the ability to receive out of band DTMF tones. Now you can disable this functionality if required. If you unselect this option, endpoints are forced to send DTMF in band (in the audio channel). This means that the MCU can pass DTMF tones on to an audio conferencing bridge or to another MCU where a conference is cascaded.

If this option is checked, the MCU will send resolutions higher than CIF to Cisco Unified Communications Manager.

Prior to Release 4.2 of the MCU, CIF was sent to Cisco Unified Communications Manager registered endpoints.

Enables the MCU to send video at 60 frames per second (fps). Note that the MCU will only send 60fps video to endpoints that it knows are capable of receiving video at that frame rate. This feature is not available on the MCU 4200 Series products.

The Motion / sharpness tradeoff option in Conference settings above should be set to Favor motion.