A name by which you will be identified should you use the text chat facility.

Note that text chat will not be available unless the MCU has the Web conferencing feature key

The numeric ID that uniquely identifies the conference you want to stream.

If the conference that you want to stream is protected by a PIN, enter it here.

Select the streaming rate you prefer to use.

There are usually two configured options for streaming rate from which you can select.

When enabled, multicast will be used when streaming this conference.

This option is not available if the streaming rate specifies that Windows Media Player will be used.

When enabled, the MCU's streaming page will attempt to access the multicast meadi stream for the chosen conference. Note that if the streaming page fails to stream the conference, you can return to the this page and clear this option; doing so will cause the MCU to attempt to stream the conference using unicast.

Select this option to stream the audio and video.

If you clear this option, then neither the audio nor video will play.

Select a size (resolution) for the video.

This option affects the size of the media player when it opens.

Select this option to stream the content channel.

If you clear this option, the content channel will not play. Clearing this option also disables text chat.

Note that text chat will not be available unless the MCU has the Web conferencing feature key; and that without the Web conferencing feature key, this option is grayed out.

Select a size for the content channel.

The configured options for streaming video.

The two options available here have been configured on the Settings > Streaming page.

If multicast is enabled for the selected streaming rate on the Settings > Streaming page and you select Prefer multicast, then multicast will be used when streaming this conference.

Multicast streaming allows an unlimited number of viewers to watch a conference on a MCU. Note that you cannot use Windows Media Player to stream in multicast mode on the MCU.

Select this option to stream the audio and video.

If you clear this option, then neither the audio nor video will play.

Select a size (resolution) for the video.

This option affects the size of the media player when it opens.

Select this option to stream the content channel.

If you clear this option, the content channel will not play. Clearing this option also disables text chat. Note that text chat will not be available unless you have the Web conferencing feature key; and that without the Web conferencing feature key, this option is grayed out.

Select a size (resolution) for the content channel.

This option affects the size of the media player when it opens.

You are scrolling up through the layout views.

You are scrolling down through the layout views.

You have stopped scrolling through the layout views.

You are scrolling through the participant list in a counter-clockwise direction.

You are scrolling through the participant list in a clockwise direction.

Speaking participant has the focus.

This participant has been given priority in the layout views.

A participant is made "important" using controls on the MCU web pages.

The audio quality from this participant is poor.

The audio quality from this participant is good.

The video quality from this participant is poor.

The video quality from this participant is good.

You are now controlling the viewing angle of the far-end video camera.

You are moving the remote far-end camera down.

You are moving the far-end video camera up.

You are moving the far-end video camera to the left.

You are moving the far-end video camera to the right.

You are zooming in with the far-end video camera.

You are zooming out with the far-end video camera.

There are both encrypted and unencrypted participants in this conference or there are streaming viewers of this encrypted conference.

This conference is being recorded.

There are audio-only participants in this conference. The number of audio-only participants is displayed next to the icon.

There are streaming participants in this conference.

The name of the conference, which is either the name entered when the conference was scheduled, or, in the case of certain specialized types of conferences, a name chosen automatically by the MCU when created.

Specialized conference types are described below in Description.

Click the conference name to display detailed information about the conference and participants.

Displays the conference streaming page. This option is not necessarily available for every conference; some users do not have access to other user's conferences. Some conferences may require a PIN to access this feature.

This option is only available if you have streaming enabled on your MCU. To enable streaming, go to Settings > Streaming.

See Using streaming to view conferences for more information.

Displays the ConferenceMe page. The ConferenceMe page allows users to join the conference using the ConferenceMe client. If they do not already have ConferenceMe installed on their computer, they can access the installer from the ConferenceMe page.

This option is only available if you have ConferenceMe enabled on your MCU. To enable ConferenceMe, go to Settings > Streaming.

See Using ConferenceMe to join conferences for more information.

Additional information about the conference, which can assist users joining conferences.

You can add the description when scheduling a conference. If you do not add a description or the conference has not been scheduled in advance, the description displays one of the following:

• <scheduled>
  The conference has been scheduled in advance using the MCU web interface, but the owner has not entered a description.
• <ad hoc>
  The conference was created dynamically during an auto attendant session and will end when the last participant using the auto attendant exits the conference.
• <auto attendant>
  This type of conference indicates that a participant is currently connected to the auto attendant and navigating the menus.

The configured owner of the conference.

See Conference ownership for additional information.

The status of a conference with respect to its H.323 gatekeeper and/or SIP registration. Depending on the conference settings, there is a maximum of four registrations for each conference: H.323 numeric ID, H.323 guest numeric ID, SIP numeric ID, and SIP guest numeric ID. The Registration field will show failed if any of the registrations has not completed successfully.

• n/a
  This conference is not configured to be registered with a gatekeeper or SIP registrar; because of this, there is no applicable registration status to show
• Registering
  This conference is in the process of registering with the gatekeeper or SIP registrar
• Failed
  At least one of the registrations for this conference has failed
• Registered
  All IDs associated with this conference have been registered successfully with the gatekeeper / SIP registrar
• Disabled
  One or more of the IDs associated with this conference has been configured to be registered with the gatekeeper or SIP registrar, but that registration has not been attempted due to another setting taking precedence. For H.323 calls this might occur if, on Settings > Gatekeeper, either the H.323 gatekeeper usage is disabled or the Allow numeric ID registration for conferences option is unselected. For SIP calls this might occur if, on Settings > SIP, the Allow numeric ID registration for conferences is unselected

Note that when there is a problem with the registration, the status is a link to the conference's Statistics page.

If the MCU can connect to an H.323 gatekeeper, each numeric ID (for both chairperson and guest privileges) for a conference can be registered with that gatekeeper as a different directory number. This allows H.323 users to dial directly into a particular conference (with the correct privileges) instead of connecting first to the MCU's auto attendant and navigating the menu system.

Likewise, if the MCU can connect to a SIP registrar, each conference can be registered with that registrar using either (or both) Numeric ID and Guest ID. This allows SIP users to dial directly into a particular conference (with the correct privileges) instead of connecting first to the MCU's auto attendant and navigating the menu system. Note that for SIP, unlike H.323, the conferences must be configured on the SIP registrar before the MCU can register them.

There is a maximum of four registrations for each conference: H.323 numeric ID, H.323 guest numeric ID, SIP numeric ID, and SIP guest numeric ID. To view further details about the registrations for a conference, click the conference name and then the Statistics tab to view the conference's Statistics page.

For tips on configuring gatekeepers, see Configuring H.323 gatekeeper settings.

For tips on configuring SIP registrars, see Configuring SIP settings.

For more information about configuring conferences (and chairperson and guest IDs and PINs), refer to Adding and updating conferences.

The number of currently active contributors to the conference. This value does not include streaming viewers or any other endpoints that are viewing only and not contributing any media to the conference.

If a limit on the number of participants has been set for the conference, the Participants value is shown as A / B, where A is the number of active participants and B is the configured limit. If it has not been possible to reserve all of the required ports for a conference (for instance because of a configuration error), this value will display in red as an error indication.

If a conference is protected by a PIN and you are not logged in as the administrator, the number of participants is hidden until the PIN is entered. In this case, the Participants value displays as <PIN required>.

When the conference began. If the conference started before today, the date also displays.

How long the conference still has to run. If the conference does not have a limited duration, this column displays as <forever>.

The name of the conference chosen when the conference was scheduled.

Click the conference name to display detailed information about the configuration of the conference and, if it is currently active, its participants.

The number that you can dial to join the conference.

Whether a PIN is required to join the conference.

The configured owner of the conference.

See Conference ownership for additional information.

Whether a conference is:

• Yet to start
  The conference's configured start time has not yet arrived.
• In progress
  The conference is running and is available for video conferencing endpoints to join. A scheduled conference in this state will also appear in the Active conferences list.
• Awaiting repeat
  The conference is not currently running, but has been previously active and is now waiting to be re-activated when the time of its next repetition is reached.

There is no explicit status for "finished" – when a conference is not in progress and is not scheduled to become active again then it is moved to the Completed conferences list.

When the conference began. If the conference started before today, the date also displays.

When the conference will end.

The name of the conference chosen when the conference was scheduled.

Click the conference name to display detailed information about the configuration of the conference.

The configured owner of the conference.

See Conference ownership for additional information.

When the conference began. If the conference started before today, the date also displays.

When the conference ended.

The name that users will see on auto attendant screens and on the MCU's web interface.

Conference names must be unique; conferences cannot share names.

Only scheduled conferences have a configurable Name. Ad hoc conferences use the 'conference number' entered by the participant who has created the conference as the Name and this is not configurable after the conference has been created.

Additional information about the conference, which can assist users joining conferences.

Use the description to provide more detailed information about the conference than the name alone conveys.

This is an optional field for scheduled conferences; ad hoc conferences cannot be given a description.

The unique identifier used for dialing in to the conference (as a chairperson participant) using an auto attendant or through an H.323 gatekeeper or SIP registrar. This number can also be used to stream the conference from the Streaming-only interface. For more information about chairpersons and guests, refer to Using IDs and PINs.

When connected to an auto attendant, participants can join a conference by typing its numeric identifier.

If you plan to allow audio-only participants, then you will need to enter either a Numeric ID or a Guest numeric ID.

If H.323 gatekeeper registration is enabled for a conference, the MCU attempts to register the conference with an E.164 telephone number, which is comprised of the Registration prefix and the numeric identifier.

If SIP registration is enabled for a conference, then the Numeric ID is registered with the SIP registrar.

Conferences that are simultaneously active must not share a Numeric ID. For example, a conference on a Tuesday and a conference on a Thursday can share a Numeric ID, whereas two permanent conferences cannot share a Numeric ID. The same number can be used for the Guest numeric ID, if there are two different PINs. Additionally, because the numeric identifier is used in gatekeeper registration, conferences and auto attendants cannot share a numeric identifier value.

For more information, refer to Using IDs and PINs.

For ad hoc conferences created via the auto attendant, the number allocated by the conference creator becomes the Numeric ID. If ad hoc conferences are registered with the gatekeeper and /or SIP registrar, participants can dial in using this number. Note that the actual number that H.323 participants will dial depends on whether prefixes are used in the Settings > Gatekeeper page.

You cannot configure the Numeric ID of an ad hoc conference; the Numeric ID of an ad hoc conference is set by the conference creator as the "conference number" at the time the conference is created.

Provides a level of security to conference access.

If a conference has a PIN set, users cannot join the conference or change its configuration without entering the correct PIN. Depending on the conference settings, it may be possible for participants to join a conference as a chairperson (using the Numeric ID and PIN), or as a guest (using the Guest numeric ID and Guest PIN).

For an ad hoc conference, you can configure a PIN both at the time of conference creation and also while the conference is running. You can also force ad hoc conference creators to use a PIN (controlled on the Settings > Conferences page).

The unique identifier used for dialing in to the conference (as a guest participant) using an auto attendant or through an H.323 gatekeeper or SIP registrar. This number can also be used to stream the conference from the Streaming-only interface. For more information about chairpersons and guests, refer to Using IDs and PINs.

When connected to an auto attendant, participants can join a conference by typing its Guest numeric ID.

If you plan to allow audio-only participants, then you will need to enter either a Numeric ID or a Guest numeric ID.

If H.323 gatekeeper registration is enabled for a conference, and you have entered a Guest numeric ID, the MCU attempts to register the conference with an E.164 telephone number, which is comprised of the Registration prefix and the Guest numeric ID.

If SIP registration is enabled for a conference, and you have entered a Guest numeric ID, then the Guest numeric ID is registered with the SIP registrar.

Conferences that are simultaneously active must not share a Numeric ID. For example, a conference on a Tuesday and a conference on a Thursday can share a Numeric ID, whereas two permanent conferences cannot share a Numeric ID. The same number can be used for the Guest numeric ID, if there are two different PINs. Additionally, because the numeric identifier is used in gatekeeper registration, conferences and auto attendants cannot share a numeric identifier value.

For more information, refer to Using IDs and PINs.

Ad hoc conferences cannot be configured with Guest numeric IDs or Guest PINs.

Provides secure access to conferences for guest participants.

If a conference has a PIN set, users cannot join the conference or change its configuration without entering the correct PIN. Participants joining as guests have restricted privileges. For more information, refer to Using IDs and PINs.

Ad hoc conferences cannot be configured with Guest numeric IDs or Guest PINs.

The owner of the conference, usually the user ID of the user account that the person who scheduled the conference logged in with.

You may or may not be able to change the conference owner, depending on your privilege level. See Conference ownership for additional information.

This setting does not apply to ad hoc conferences.

Enables the MCU to attempt to register the Numeric ID and/or Guest numeric ID with the configured H.323 gatekeeper and/or SIP registrar.

To globally enable the MCU to allow conferences to register to the SIP registrar, go to Settings > SIP and select Allow numeric ID registration for conferences.

To globally enable the MCU to allow conferences to register to the gatekeeper, go to Settings > H.323 and select Allow numeric ID registration for conferences.

This setting applies to both the Numeric ID and Guest numeric ID (if you have set both). For more information, refer to Using IDs and PINs.

For ad hoc conferences, whether or not they are registered with the gatekeeper and/or SIP registrar depends on the Numeric ID registration setting on the ad hoc conferences template. You can edit the Numeric ID registration setting for individual active ad hoc conferences. For more information about templates, see Using conference templates.

For scheduled conferences, whether or not they are registered with the gatekeeper and/or SIP registrar depends on the configuration of the individual conference's Numeric ID registration setting.

Controls what happens to the conference when the last participant with chairperson status leaves the conference. The options are:

• Disconnect all participants: this is the default option. When the last participant with chairperson status leaves the conference, all other participants will be disconnected
• Take no action: all participants may continue the conference until the last one disconnects

This setting applies to scheduled conferences that include guest participants (that is, those who have joined the conference using the Guest numeric ID (and PIN if one was set).

Controls "Floor and chair control" settings for this conference. The options are:

• Do not allow floor or chair control: the use of floor and chair controls is not allowed in this conference
• Allow floor control only: only floor control is allowed in this conference; chair control is not allowed. Any participant can 'take the floor' so long as no other participant has currently 'taken the floor'
• Allow floor and chair control: both floor and chair control are allowed in this conference. Any participant can take the floor, and any chairperson participant can take the chair so long as no other participant has currently done so

Some H.323 endpoints support a feature known as floor and chair control that is encompassed by the H.243 protocol. For more information, refer to H.243 floor and chair control.

If you change the Floor and chair control setting for a conference currently taking place, there will be no immediate effect. That is, an existing floor or chair participant will not have that status removed.

If the unit-wide Floor and chair control setting on the Global conference settings page is set to Disabled, it will not be possible to use floor or chair control operations in any conference.

For ad hoc conferences, you can configure the Floor and chair setting through the ad hoc conferences template. You can also edit the Floor and chair setting for active ad hoc conferences.

Select if you want the loudest speaker to appear full screen to the other participants in a conference. If the conference requires this functionality, choose how quickly the loudest speaker will appear in full-screen view to the other participants. Choose from:

• Immediately: As soon as the MCU identifies a participant as the loudest speaker, the MCU will show that participant in full screen to the other participants in the conference. The loudest speaker will continue to see their normal continuous presence conference view. If another participant interrupts the loudest speaker, that participant becomes the loudest speaker and will be seen in full screen by the other participants (and that participant will see their normal continuous presence view).
• After 10 seconds: When the MCU identifies a participant as the loudest speaker, if that participant continues to be the loudest speaker for 10 seconds then the MCU will show that participant in full screen view to the other participants. The loudest speaker will continue to see their normal continuous presence conference view. If another participant interrupts the loudest speaker, everyone will immediately see their normal continuous presence view. If the interrupter continues to speak for 10 seconds, the MCU identifies that participant as the loudest speaker who will then be shown in full screen to the other participants (and the new loudest speaker will continue to see their normal continuous presence view).
• After 30 seconds: As for After 10 seconds, but the MCU waits for 30 seconds before showing the loudest speaker in full screen view.
• After 1 minute: As for After 10 seconds, but the MCU waits for one minute before showing the loudest speaker in full screen view.
• Disabled: The loudest speaker will not be shown in full screen view to the other participants. All conference participants will see the normal continuous presence conference view, or a custom layout if one has been specified.

This setting is most useful where the conference is a lecture.

Automatic lecture mode allows a lecturer to be shown in full-screen view to the students. In this mode, the lecturer will continue to see their normal (continuous presence) view. That is, the lecturer will see the students and not himself.

The MCU identifies the lecturer as being the loudest speaker.

If you have configured a custom layout for the lecturer, that will override the normal continuous presence view. For the other participants (the students), the view of the lecturer (the loudest speaker) overrides any custom layout.

Note that you can use the conference's Mute on join setting together with the settings for the lecturer's endpoint's Initial audio status to ensure that the full screen view does not get needlessly interrupted.

If you disable Automatic lecture mode, this change will take effect when the MCU identifies a new loudest speaker.

For ad hoc conferences, you can configure Automatic lecture mode through the ad hoc conferences template. You can also edit the Automatic lecture mode setting for individual active ad hoc conferences.

Indicates the visibility of the conference on the auto attendant and the web interface. The options are:

• Public: the conference will be listed in the auto attendant and be visible to all users of the web interface
• Private: the conference will not be listed in any auto attendant except for auto attendants specifically set to show it. The conference will also only be visible in the web interface to the conference owner and to the admin user

For private conferences not visible on an auto attendant, participants will still be able to join the conference if they know the PIN.

Note that only admin users can choose which conferences are visible on a given auto attendant.

For ad hoc conferences, you can configure Visibility through the ad hoc conferences template. You can also edit the Visibility setting for individual active ad hoc conferences.

For more information, refer to Adding and updating an auto attendant.

The encryption setting for this conference, if you have the encryption feature key enabled.

If encryption is enabled unit-wide (through the Settings > Encryption page), you can set one of:

• Required: encryption must be used for this conference
• Optional: encryption is optional for this conference

This setting is grayed-out if encryption is disabled on the Settings > Encryption page.

Note that to be able to use encryption, the Encryption feature key must be present on the MCU.

Prevents or permits conference participants changing their view layout or focused participant using Far-end Camera Control (FECC) or DTMF tones. Choose from:

• Disabled: in this conference, participants will not be allowed to change their view layout using either FECC or DTMF, unless you have overridden this setting in an endpoint's individual configuration
• FECC only: in this conference, participants will be only be allowed to change their view layout using FECC, unless you have overridden this setting in an endpoint's individual configuration
• FECC with DTMF fallback: in this conference, participants will be allowed to change their view layout using FECC. If FECC is not available, this participant will be able to use DTMF

You may wish to prevent participants from changing their view layout in a managed conference, or classroom environment.

This is a per-conference option, but you can still configure Layout control via FECC / DTMF on a per-participant basis.

For ad hoc conferences, you can configure Layout control via FECC / DTMF through the ad hoc conferences template. You can also edit this setting for individual active ad hoc conferences.

When calling out to an endpoint, if you have configured Layout control via FECC / DTMF for that endpoint, it will override this setting (otherwise the endpoint will use the conference configuration for this setting).

This setting will apply to endpoints which connect to the conference via an auto attendant or by dialing in directly.

Set the option for the muting of in-band DTMF sent from endpoints in this conference. Note that this sets the conference configuration for this option, but you can also override it for individual endpoints in the conference (through the configuration of the individual endpoints). Choose from the following (the setting will be applied to all endpoints in the conference that are configured to use the conference configuration for Mute in-band DTMF):

• Never: the in-band DTMF will never be muted. Any DTMF tones sent from these endpoints will be audible to conference participants.
• Always: the in-band DTMF will always be muted. Any DTMF tones sent from these endpoints will not be audible to conference participants.
• When used for MCU control: if a participant is using in-band DTMF to control conference layout and for other in-conference features, the tones will be muted and will not be audible to conference participants. The MCU will only expect a participant to use DTMF for MCU control if Layout control via FECC / DTMF is set to FECC with DTMF fallback and FECC is unavailable to the endpoint.

This is a per-conference option, but you can still enable or disable the muting of in-band DTMF on a per-participant basis.

In some circumstances, you might need to override this setting for individual endpoints. For example, where a conference is cascaded onto an audio bridge, it might be useful for one of the participants in that conference to be able to send in-band DTMF to the MCU. This is for the purposes of sending the conference ID or PIN to the audio conferencing bridge. In this case, the Mute in-band DTMF setting for the endpoint of that participant needs to be Never (and you configure this in an endpoint's configuration, see Configuring an H.323 endpoint and Configuring a SIP endpoint).

For ad hoc conferences, you can configure the Mute in-band DTMF setting through the ad hoc conferences template. You can also edit the Mute in-band DTMF setting for individual active ad hoc conferences.

• Enabled: When this setting is enabled, a participant in this conference can mute their audio by typing *6 into their DTMF (number) keypad.
• Disabled: For participants in this conference, pressing *6 on an endpoint's number keypad achieves nothing.

This can be useful for participants calling into a conference on a traditional, audio-only phone. Sometimes there is no other control for muting audio on these phones.

When enabled, participants can turn off their microphones (mute their audio) by pressing *6; pressing *6 again turns the microphone on again.

For ad hoc conferences, you can configure the Allow DTMF *6 mute audio setting through the ad hoc conferences template. You can also edit it for individual active ad hoc conferences.

Indicates when the MCU should invite any pre-configured endpoints into a conference. The options are:

• At the start of the conference
  Pre-configured participants will be called as soon as the conference starts.
• When at least one other participant is present
  Pre-configured endpoints will only be called after at least one other participant joins the conference.

Select which option fits your requirements best. Calling pre-configured endpoints at the start of the conference is most appropriate for repeating conferences with a particular start time.

Calling pre-configured endpoints when at least one other participant is present is most appropriate for permanent conferences; such conferences are typically un-attended for much of the time, and it may only be useful to invite pre-configured endpoints when others are present.

This setting only applies to scheduled conferences.

Select to initially mute audio and/or video from all participants when they join the conference.

If you select to mute audio on join, when a participant dials-in to a conference, he will not be able to contribute audio to the conference. If you select to mute video on join, when a participant dials-in to a conference, he will not be able to contribute video to the conference. You can mute both audio and video if required.

This can be altered during the course of the conference by going to Conferences and clicking on the name of a conference and altering a participant's settings. For more information about altering a participant's settings during a conference, refer to Viewing the conference participant list.

Note that for pre-configured participants and for participants to whom the MCU dials out, the Initial video status and Initial audio status settings will be used to determine whether or not audio and video contributions are muted. For more information about dialing out to participants, refer to Adding participants. For more information about pre-configured participants, refer to Configuring an H.323 endpoint and Configuring a SIP endpoint

For an ad hoc conference, you can configure the Mute on join setting through the ad hoc conferences template. You can also edit the Mute on join setting for active ad hoc conferences.

Allow unicast and multicast streaming access to individual conferences.

For an ad hoc conference, you can configure Streaming through the ad hoc conferences template. You can also configure Streaming for active conferences.

To use streaming, it must be enabled unit-wide on the Settings > Streaming page. See Configuring streaming settings for additional information.

If Enabled, this conference is able to support an additional video stream, sent potentially to all connected endpoints, intended for showing content video.

This content video is typically high resolution, low frame rate data such as a presentation formed of a set of slides. Such presentation data can be sourced by:

• an endpoint specifically contributing a separate content video stream,
• the MCU being configured to use an endpoint's main video stream as the conference's content channel,
• a dedicated VNC connection,
• or user-generated markup data (the markup is normally, though not always, used in conjunction with content video or VNC data).

For ad hoc conferences, whether or not content channel video is allowed is controlled by the Content channel video setting in the ad hoc conference template.

To use content, it must be enabled unit-wide on the Settings > Content page. See Configuring content settings for additional information on MCU-wide content configuration parameters.

Whether, by default, endpoints are permitted to contribute the content channel for a conference through the mechanism of opening a content video channel.

There can only be one endpoint contributing content video at any one time, and the MCU arbitrates between them. Therefore, even with this parameter set to Enabled, the ability of the endpoint to contribute content video will be affected by other endpoints' behavior.

If this setting is Disabled, it is still possible to enable content contribution on a per-endpoint basis when the conference is active. Similarly, it is possible to disable content contribution from specific endpoints, either while they are connected or via their configuration. For more information about endpoint configuration, refer to Configuring H.323 endpoints and/or Configuring SIP endpoints.

This setting only applies to scheduled conferences. For ad hoc conferences, whether or not endpoints are allowed to contribute content is controlled by the Content contribution from endpoints setting in the ad hoc conference template.

To use content, it must be enabled unit-wide on the Settings > Content page. See Configuring content settings for additional information on MCU-wide content configuration parameters.

Choose the resolution for the content channel that will be transmitted to endpoints in this conference:

• 4:3 resolutions only: the MCU will encode the content and transmit it in a resolution of ratio 4:3
• 16:9 resolutions only: the MCU will encode the content and transmit it in a resolution of ratio 16:9
• Allow all resolutions: the MCU will decide on the most optimal resolution depending on information about capabilities sent by the endpoints in the conference

For ad hoc conferences, transmitted content resolution is controlled by the ad hoc conference template.

When the MCU is not in port reservation mode, this parameter sets a limit on the number of endpoints which can connect to the conference as video participants.

A participant counts (as a single unit) towards the video limit whether the MCU is sending a video stream to that participant or a video stream is being received.

If you do not want to limit the number of participants who can join this conference and use video, leave this field blank.

This field is only shown if the MCU is not in port reservation mode.

This field only applies to scheduled conferences.

When the MCU is not in port reservation mode, this parameter sets a limit on the number of endpoints which can connect to the conference as audio-only participants.

A participant counts (as a single unit) towards the audio limit whether the MCU is sending an audio stream to that participant or an audio stream is being received.

If you do not want to limit the number of participants who can join this conference to use just audio, leave this field blank.

This field is only shown if the MCU is not in port reservation mode.

This field only applies to scheduled conferences.

In port reservation mode, this parameter specifies the number of video ports to reserve.

A participant counts (as a single unit) towards the video reservation value whether the MCU is sending a video stream to that participant or a video stream is being received.

This value is both a reservation and a limit; the MCU guarantees that this many video participants can connect to the conference, but no more than this will be able to join.

This field is only shown if the MCU is in port reservation mode.

In port reservation mode, this parameter specifies the number of audio-only ports to reserve.

A participant counts (as a single unit) towards the audio reservation value whether the MCU is sending an audio stream to that participant or an audio stream is being received.

This value is both a reservation and a limit; the MCU guarantees that this many audio-only participants can connect to the conference, but no more that this will be able to join.

This field is only shown if the MCU is in port reservation mode.

The time at which the conference will begin.

The date on which the conference will begin.

Sets the conference start time to the current time on the MCU.

The current time on the MCU is determined by the settings in the Settings > Time page, which can only be modified by the administrator. See Displaying general status for additional information.

Allows you to retain a conference and its settings for an infinite period of time.

Limits the duration of the conference for one instance of the conference.

These fields are not available or necessary for conferences set to permanent.

Which days and / or weeks the conference repetitions will occur.

The repetitions will always start at the same time of day: the conference's configured Start time (see above), and will last for the same amount of time: the configured Maximum duration.

The start date is taken into account when determining when the first repetition should occur. For instance, if the start date is a Wednesday and the conference is scheduled to repeat every Monday, Tuesday and Wednesday then it will occur only on Wednesday in the first week and on all three specified days in subsequent weeks.

If a conference is set to repeat, its repetitions can be configured to go on forever, stop after a certain date, or to occur only a certain number of times.

The first activation of a conference counts as a "repetition", so configuring a conference to repeat but terminate after 1 repetition is equivalent to it not repeating at all.

Users with these privilege levels are able to create and own conferences, and are able to exercise full control of all conferences.

Users with these privilege levels are able to create and own conferences. They have full control of conferences they own, and limited control of conferences owned by other users.

Users with these privilege levels are able to create and own conferences. They have full control of conferences they own, but no control of conferences owned by other users.

Users with these privilege levels are not able to own conferences or change any conference's configuration.

This level of control permits the following operations:

Participant control
With full conference control, a user is able to disconnect participants, connect new participants to the conference, and end the conference whenever they want to.

Configuration access
A user with full conference control can view and modify any aspect of the conference's configuration. This includes the start time, end time, or repetition characteristics, whether streaming is enabled, and which endpoints are pre-configured as participants.

Changing live conference parameters
When the conference is in progress, a user with full control is permitted to send a text message to all connected participants' video displays and change the Conference custom layout.

Additionally, full control includes all of the operations covered by limited control, detailed below.

This level of control permits the following operations:

Viewing the participant list
The participant list shows the names of the endpoints currently connected to the conference, a summary of that endpoint's status and, if they are a video participant, a thumbnail preview image of the video stream they are supplying. Thumbnail previews are shown by default, but you can configure the user interface not to show them. The setting that controls this is the Show video thumbnail images option on the Settings > User interface page. Note that the MCU will not show thumbnail previews on the participant list page if encryption is required for a conference. However, thumbnail previews will be shown for conferences where encryption is optional and there are encrypted participants.

Via the participant list, it is also possible to mute (or stop muting) individual endpoints' audio, change the conference's "important" participant, and enable or disable the participants' ability to affect their own layouts via Far-End Camera Control or DTMF tones.

Controlling video sent to participants
This includes being able to choose what view layout (or family) is used for constructing the conference view being sent to a participant, changing the Participant custom layout, and whether to send widescreen or standard format video to that endpoint.

Controlling participant cameras
The web interface can be used to send control commands (e.g. pan and tilt) to a remote participant's camera.

Viewing audio status
Waveforms of audio channels being sent to, and received from, the participant can be viewed, audio gain applied, and participant audio can be muted if required.

Sending messages to individual participants
Textual messages can be sent to an individual participant, and will appear on their displays.

Viewing participant statistics and diagnostics
This allows details of the media streams being sent to, and received from, participants to be viewed, plus endpoint-specific characteristics to be examined.

This means that none of the above operations are possible. Depending on the specific privilege level, either the list of scheduled conferences will not be shown to the user, or the list will be shown but conferences over which the user has no control will be presented as names rather than hyperlinks.

Whether a custom layout can be used for this participant.

When you click a new layout from the Available layouts, Enabled is automatically chosen with the most recent layout selected.

New participants joining this conference will view the conference with this custom layout rather than one of the default views (see Customizing a participant's layout display).

To force all participants to use this layout, click Switch all participants to this view.

If a participant has chosen to use a custom conference layout (see Customizing a participant's layout display), their view will automatically update and switch to the new view.

Displays all the conference layouts that are available. Click a layout to select it and make it available.

You can only select one custom layout at a time.

When the conference started.

When the conference will complete. This will be the time at which the maximum duration of the conference will have elapsed. This setting displays as <permanent> if it has been configured to last forever.

The duration of this conference.

The status of a conference with respect to its H.323 gatekeeper and/or SIP registrations. The possible states are:

• n/a
  This conference is not configured to be registered with a gatekeeper or SIP registrar; because of this, there is no applicable registration status to show.
• <number> registered
  The conference has been registered successfully with the gatekeeper or SIP registrar and can be contacted using the number indicated.
• Registering
  This conference is in the process of registering with the gatekeeper or SIP registrar.
• Deregistering
  The conference is in the process of unregistering with the gatekeeper or SIP registrar. This might occur if:
  • Gatekeeper registration has been turned off (either for that conference only or for the entire MCU)
  • The configured gatekeeper has just been changed and the MCU is in the process of unregistering from the previous gatekeeper before registering its conferences with the new one.
• Re-registration pending / Retry timeout
  If the MCU fails to register a conference with the gatekeeper or SIP registrar, it enters these states temporarily before re-attempting the registration.
• Registration disabled
  This ID has been specifically configured to be registered with the gatekeeper or SIP registrar, but some other configuration has overridden this, causing the registration to not be attempted. This state might occur if either of the H.323 gatekeeper usage or ID registration for scheduled conferences options on the Settings > Gatekeeper page is set to Disabled.
• <no ID set>
  The conference is configured to register with a gatekeeper or SIP registrar, but has not had a numeric identifier set.

The current number of contributing audio/video participants.

The largest number of contributing audio/video participants who have been in the conference at the same time.

The current number of contributing audio-only participants.

The largest number of contributing audio-only participants who have been in the conference at the same time.

The current number of streaming participants watching the conference.

The largest number of streaming participants who have been watching the conference at the same time.

Enter the message to send to all conference participants.

Messages must be fewer than 256 characters, but depending on the viewing screen, messages at the higher-end of this limit might not display properly. Therefore, consider limiting messages to approximately 180 characters. Messages longer than 256 characters will not be truncated; they will not display at all.

You can disable this setting from Settings > Conferences (see Conference settings).

The vertical position of the message on the conference display.

Select from the top, middle, or bottom of the conference display.

How long the message appears on participants' video screens.

The default setting is 30 seconds. To remove all messages before they time out, click Clear message.

Indicates whether the participant's endpoint is an H.323, SIP, or VNC endpoint.

Displays the name of the endpoint.

The following may also be displayed:

User: <user id>
If the participant has been resolved to a particular configured user (for instance by matching the participant's E.164 phone number against a configured value), then the appropriate user id will be shown here.

User names only display if the participant list is being viewed by an administrator, because only administrators have access to the configured user database.

Configuration: <name>
This indicates that this participant corresponds to a pre-defined endpoint. The <name> shown is the endpoint's configured name.

Configured endpoint names only display if the participant list is being viewed by a user whose privilege level is administrator or conference creation and full control; only users with these privilege levels have access to the configured endpoint database.

 Makes participant important

 Makes participant unimportant

When you make a participant "important", it sets this participant as the focused participant. For example, this participant is considered the loudest participant even if they are not speaking.

Only one participant can be identified as "important", and no participant is set to "important" by default.

This option affects the layout views for the conference and individual participants. See Selecting a custom participant view and Customizing layout views.

If the content channel is made "important", one participant can still be important. On endpoints that support content, the content channel will be displayed in the content channel window and the important participant will be given the focus in the main video window. On endpoints that do not support content, the important participant will be ignored as the content channel will be given the focus.

 Prevents other participants from hearing this participant (mute).

 Allows other participants to hear this participant's audio (stop muting)

Prevents others from seeing this participant's video contribution (mute).

Allows others to see this participant's video contribution (stop muting).

The presence of these controls is controlled by the Participant list controls setting on the Settings > User interface page (refer to Customizing the user interface).

  Disconnects a participant from the conference

You can configure the MCU to require confirmation when someone attempts to disconnect an individual participant from a conference. This setting is on the Settings > User interface page.

Displays the time at which a participant connected to the conference. If a participant is not yet fully connected (for example, if the MCU has called a participant but it has not yet answered), then that is indicated here. The resolution of the participant's video stream is also displayed.

The following additional indications may also be displayed:

If this column is selected as the sorting field, the listing is ordered according to when the participants connected to the conference.

Recording
Indicates that the conference is being recorded.

Encrypted
Indicates that all media streams in both directions (to and from the endpoint and the MCU) are encrypted.

Rx encrypted
Indicates that all media streams received from this participant are encrypted.

Tx encrypted
Indicates that all media streams sent to this participant are encrypted.

Next to the encryption indication is the AES check code. This can be used in combination with information displayed by some endpoints to check that the encryption is secure.

Pre-configured
This indicates that this participant is in the conference because of a pre-configured endpoint.

See Adding pre-configured participants for additional information on adding endpoints to conferences in this way.

No audio capabilities
No video capabilities
These messages indicate that the MCU has not opened a media channel to a participant's endpoint because it has no capability to receive that type of channel. For example, if the endpoint is a simple telephone, you might expect to see "No video capabilities" shown here.

No common audio codecs
No common video codecs
These messages indicate that the remote endpoint had declared media capabilities, but the MCU was not permitted to open a channel that the endpoint was prepared to receive.

This is most likely to occur if you have disabled one or more codecs in the "Audio codecs from MCU" or "Video codecs from MCU" configuration on the Advanced conference settings web page.

No common audio formats
No common video formats
These messages indicate that the remote endpoint had declared media capabilities including codecs that the MCU was permitted to send, but that the MCU was unable to transmit the specific formats declared.

This could occur if, for instance, the far end's advertised receive video sizes were all 4CIF (704 x 576 pixels) or above, and the MCU was set to not transmit above CIF (352 x 288 pixels).

No common symmetric audio codecs
No common symmetric video codecs
Indicates that the MCU was unable to open a media channel to the endpoint because the only possible channels it would be able to open were invalid due to a symmetry clash. This clash occurs when the remote endpoint declared that it is only able to receive certain types of media if it is also sending the same format, and the format in question is one that the MCU is able to send but not receive.

Audio port limit exceeded
Video port limit exceeded
These messages occur if a channel was unable to be opened solely because doing so would have exceeded the port limit. This limit may be a per-conference restriction or, for those conferences which impose no such limit, it could be that all of the MCU's available ports were in use.

Endpoint audio and video channels rejected
Endpoint audio channel rejected
Endpoint video channel rejected
Indicates that the MCU is unable to receive the media format that the endpoint is trying to transmit.

Tx:
Rx:
These status rows show details of the audio and (main) video streams being sent to or received from the endpoint.
Tx refers to media streams sent by the MCU, and Rx means media streams being received by the MCU.

If the MCU has received information that the endpoint has been muted at the far end, this will be indicated in the Rx row as "muted remotely".

Content tx: <status>
This row (if present) shows one of two things: the characteristics of the content video channel being sent by the MCU to a participant, or the reason why no such stream is currently being transmitted. The status values that can be shown here are:

Content tx: pending
The MCU is able to send content video to the participant but is not currently doing so. This is normally because there is no active content channel video source for the conference. This status will also be shown for a participant which is the content channel video source and is also capable of receiving the currently active content video stream.

Content tx: disabled
Content is enabled for this conference, but this participant is not allowed to receive it. To enable content for this participant, configure the Content video receive setting for this participant's endpoint (refer to Configuring H.323 endpoints), or use the enable control for an active call.

Content tx: no common codecs
There is a unit-wide setting that determines which video codec is used by the MCU for outgoing content channels. The Outgoing content video codec is on the Settings > Content page.

This message means that the endpoint is able to receive content video, but not using the same codec as the MCU is configured to transmit.

Content tx: resolution mismatch
Content tx: bit rate mismatch
For each conference, the MCU uses a single video stream for all outgoing content connections to endpoints. This entails considering all endpoints' receive capabilities and deciding which resolution and bit rate to send in order to maximize the number of content channel viewers. These messages mean that the MCU has been unable to include this endpoint in the set of content viewers because of its limitations with regard to video resolution or bit rate. Note that it is possible to configure a lower limit on the bandwidth of the shared content video encoding which will cause a bit rate mismatch where an endpoint is only able to receive a low bit rate stream (refer to Configuring content settings).

Content tx: no common formats
This conference's configuration specifies that the content channel is transmitted in 16:9 resolutions only. However, this endpoint does not support 16:9 resolutions. To allow the MCU to select a content resolution that will accommodate the capabilities of all endpoints in the conference, change the Transmitted content resolutions setting in the conference's configuration to Allow all resolutions.

No Content tx status will be shown if the conference does not have content channel video enabled, or if the endpoint has no content capabilities.

You may change whether the MCU is prepared to send the conference content channel stream to an endpoint using content using the enable or disable control here. If sending of content video to an endpoint is currently not allowed, you will see the enable option, otherwise you will see the disable option.

For more information about using content, refer to Content channel video support.

Content video source (main video)
Content video source
The associated participant is currently supplying the conference's content channel video.

Content: unable to use main video as source
Use of this participant's main video source as the content (content channel) source has failed. This is normally because there is already a source for the content channel; either another participant's main video channel which has been configured in the same way (VNC participants are set up this way by default) or a content video channel contributed by a connected endpoint.

Packet loss detected
This message appears if packet loss is detected between the MCU and the endpoint.

Click View to open the Participant statistics page and display details about the connection, for example the packet errors. See Displaying statistics for a participant.

Conference chair
This endpoint has requested and been granted the chair.

For more information, refer to H.243 floor and chair control.

Active floor

The endpoint has requested and been granted the floor and its media is being broadcast to all endpoints in the conference.

For more information, refer to H.243 floor and chair control.

Inactive floor

This endpoint believes it has been granted the floor, but its media is not being shown to all endpoints in the conference.

This situation can occur when an endpoint requested the floor, was granted the floor, and was then moved to another conference where there was already an active floor participant.

For more information, refer to H.243 floor and chair control.

Assigned floor

This endpoint's media is being broadcast to all endpoints in the conference, although it did not request the floor itself.

This situation can occur if another endpoint, while chair, has issued H.243 commands to make that endpoint the floor.

For more information, refer to H.243 floor and chair control.

Cascade link to master
Cascade link from slave
Indicates that this connection is a cascade link to or from another conference.

Displays a sample still video capture of the participant.

Click the picture to update it.

Note that conferences that are configured to require encryption do not show previews. Also note that previews can be disabled on theSettings > User interface page (refer to Customizing the user interface).

Controls

These controls are only available if the conference is configured with content enabled, and if the participant is contributing a main video channel.

 This control causes the MCU to attempt to use the participant's main video channel as the conference's content channel source. This will not be possible if the conference already has an active content channel source (either an endpoint's content video channel or another participant's main video activated via this control).

 This control causes the MCU to stop attempting to use the participant's main video channel as the conference's content channel source. It is necessary to use this control to switch to using a different endpoint's primary video channel or to enable content video contribution from endpoints.

See Content channel video support for additional information on H.239 and BFCP.

Displays static sample of video screen in the currently selected layout.

Click on the image to refresh the picture

Adds a border thickness to display around the video image.

If the image is displaying off the edges of the participant's screen, add a border until the image displays properly.

Give prominence to one participant over the others.

The number of contributing conference participants determines the size of the large pane.

Displays a single participant.

Displays the four most active participants without seeing them scaled down to a small size if there are lots of other participants.

Used when there are five or more video participants.

Gives equal prominence to up to 20 conference contributors, and is useful for a "roll call" of active participants.

The MCU automatically changes the layout to the 3 x 3 arrangement, and will continue to use this layout for up to 9 participants. With 10 or more participants, the 4 x 4 view is used, and with 17 or more participants the 5 x 4 view will be used. The MCU will then continue to use this layout even if there are more than 20 participants.

Gives prominence to two participants in the center of the view while showing smaller versions of other participants' video streams above and below.

This view is useful for observing a dialog between two participants or for viewing slides and a presenter.

Click Edit to choose or create a custom layout to be used by any participant.

See Customizing layout views.

Click Edit to choose a pre-configured custom layout for this participant.

See Selecting a custom participant layout.

Prevents this participant from changing their own conference layout using the far-end camera controls on their video endpoint.

A participant can still change their layout view using the web interface.

Allows this participant to control their own conference view.

Send "normal" format video to this participant - this means that the video is intended to be displayed on a screen whose dimensions (width and height) are in the ratio 4:3.

The available options for the resolution of transmitted video are controlled by the Transmitted video resolutions setting which can be configured for the whole unit on the Settings > Conferences page or per configured endpoint (refer to Configuring an H.323 endpoint and/or Configuring a SIP endpoint).

Send "widescreen" format video to this participant - this means that the video is intended to be displayed on a screen whose dimensions (width and height) are in the ratio 16:9.

Do not allow this participant to start contributing content channel video.

For more information, see Content per-participant parameters.

Allow this participant to start contributing content channel video.

Indicates which participant appears in the largest pane.

Depending on the types of participant in the conference (i.e. content channel, endpoint, audio-only participant), you can select from these options:

• Voice-switched: the loudest participant will given the largest pane in the conference (the default setting)
• Content channel: the content channel will be given the largest pane in the conference
• <participant name>: the participant that you select will be given the largest pane in the conference

This setting will be overridden if a participant is identified as "important" on the Conference Participants List (see Viewing the conference participants list).

Click on one of the directional arrows to change the view direction of the camera.

Not all endpoints will respond to these controls. In particular, endpoints with fixed cameras such as most webcams.

Click on one of the magnifying options to zoom the view in or out.

Not all endpoints will respond to the zoom controls, possibly including those that do respond to the Movement controls

Click on one of the adjustment options to improve the clarity of the image.

Not all endpoints will respond to the focus controls, possibly including those that do respond to the Movement controls

Prevents others from seeing this participant's video in conference views (mute).

This setting applies only to conference views. The participant's video will still appear in the conference participant list (see Viewing conference participants list), and in the auto attendant if a conference is not PIN-protected (see Using an auto attendant).

Allows others to see this participant's video in conference views (stop muting)

Prevents others from hearing this participant (mute).

Allows others to hear this participant's audio (stop muting).

Indicates whether a custom layout can be used for this participant.

When you click a new layout from the Available layouts, Enabled is automatically chosen with the most recent layout selected.

Displays all pre-configured layouts that are available to the participant. Click a layout to select it and make it available for the participant.

You can only select one custom layout per participant.

These layouts are designed to be suitable for all video conferencing situations:

These layouts are designed to be suitable for displaying composed views of standard (4:3) video streams on widescreen (16:9) displays:

The audio codec in use, along with the current packet size (in milliseconds) if known.

If the MCU has received information that an endpoint has been muted at the far end, this will be indicated here.

The IP address and port from which the media is originating.

Whether or not encryption is being used on the audio receive stream by this endpoint.

This field will only appear if the encryption feature key is present on the MCU.

The apparent variation in arrival time from that expected for the media packets (in milliseconds). The current jitter buffer also displays in parentheses.

You should expect to see small values for this setting. Consistently large numbers typically imply potential network problems.

The jitter buffer shows the current playout delay added to the media to accommodate the packet arrival jitter. Large jitter values indicate a longer buffer.

Represents the audio volume originating from the endpoint.

The number of audio packets destined for the MCU from this endpoint.

The number of packet errors, including sequence errors, and packets of the wrong type.

You should expect to see small values for this setting. Consistently large numbers typically imply potential network problems.

Frame errors, as A/B where A is the number of frame errors, and B is the total number of frames received.

A frame is a unit of audio, the size of which is dependent on codec.

You should expect to see small values for this setting. Consistently large numbers typically imply potential network problems.

If the time stamps or marker bits (or both) are detected to be unreliable in the incoming video stream, information will be displayed here.

This field is not displayed when there is no problem with the time stamps and marker bits. Where there is a problem the following text is displayed: "Media timestamps unreliable", "Media marker bits unreliable", or both if both conditions detected.

The audio codec being sent from the MCU to the endpoint, along with the chosen packet size in milliseconds.

The IP address and port to which the media is being sent.

Whether or not encryption is being used on the audio transmit stream by this endpoint.

This field will only appear if the encryption key is present on the MCU.

A count of the number of packets that have been sent from the MCU to the endpoint.

The IP address and port to which RTCP (Real Time Control Protocol) packets are being sent for the audio and video streams.

A count of the number of "receiver report" type RTCP packets seen by the MCU.

A single RTCP packet may contain more than one report of more than one type. These are generally sent by any device receiving RTP (Real Time Protocol) media from the network and are used for auditing bandwidth, errors, and so on by the MCU.

A count of the reported packet loss on the control channel.

A count of the number of "sender report" type RTCP packets sent by the MCU.

These are typically sent by any device that is sending RTP media.

The IP address and port to which the MCU is sending RTCP packets about this stream.

A count of the number of "receiver report" type RTCP packets seen by the MCU.

A single RTCP packet may contain more than one report of more than one type. These are generally sent by any device receiving RTP (Real Time Protocol) media from the network and are used for auditing bandwidth, errors, and so on by the MCU.

A count of the number of "sender report" type RTCP packets received by the MCU.

These are typically sent by any device that is sending RTP media.

A count of the number of packets that have been sent from the MCU to the endpoint.

The codec in use and the size of the picture that the MCU is receiving from the specific participant. If the picture is a standard size (for example, CIF, QCIF, 4CIF, SIF) then this name is shown in parentheses afterwards.

The IP address and port (<IP address>:<port>) of the device from which video is being sent

Whether or not encryption is being used on the video receive stream from this endpoint.

This field will only appear if the encryption key is present on the MCU.

The negotiated bit rate available for the endpoint to send video in.

This value represents the maximum amount of video traffic that the remote endpoint will send to the MCU. It may send less data than this (if it does not need to use the full channel bit rate or the MCU has requested a lower rate), but it should not send more.

The bit rate (in bits per second) that the MCU has requested that the remote endpoint sends. The most-recently measured actual bit rate displays in parentheses.

This value might be less than the Channel bit rate if:

• the MCU detects that the network path to the remote endpoint has insufficient capacity to maintain a higher traffic rate
• that endpoint's video stream's position in the active conference compositions does not require it
• it has been necessary to reduce the video bit rate because of the overall call bit rate; the audio bit rate plus the video bit rate should not exceed the call bit rate

For example, if all participants in the conference were watching a single participant at full screen, no other participants' video streams would be needed at all. So the MCU would request that those streams were sent at a low bit rate in order to avoid needless use of network bandwidth.

If the receive bit rate has been limited to below the maximum channel bit rate, the reason for this limitation can be seen by moving over the icon.

Represents the variation in video packet at arrival time at the MCU.

The number of milliseconds by which the video follows the audio. Some endpoints send audio and video out-of-sync. The MCU ensures audio and video are played together.

The number of video packets destined for the MCU from this endpoint

Video packet-level errors such as sequence discontinuities, incorrect RTP details, and so on. This is not the same as packets where the content (the actual video data) is somehow in error.

This value does not represent packets in which the actual video data in the packets is in error.

The frame rate of the video stream currently being received from the endpoint.

The number of frames with errors versus the total number of video frames received.

The codec, size and type of video being sent from the MCU to the endpoint.

The IP address and port of the device to which the MCU is sending video.

Whether or not encryption is being used on the video transmit stream to this endpoint.

This field will only appear if the encryption key is present on the MCU.

The negotiated available bandwidth for the MCU to send video to the endpoint in.

The bit rate the MCU is attempting to send at this moment, which may be less than the channel bit rate which is an effective maximum. The actual bit rate, which is simply the measured rate of video data leaving the MCU, displays in parentheses.

The Transmit bit rate value might be less than the Channel bit rate if :

• the remote endpoint receiving the video stream from the MCU has sent flow control commands to reduce the bit rate
• it has been necessary to reduce the primary video bit rate to allow sufficient bandwidth for a content video stream

If the transmit bit rate has been limited to below the maximum channel bit rate, the reason for this limitation can be seen by moving over the icon.

The number of video packets sent from the MCU to this endpoint.

The frame rate of the video stream currently being sent to the endpoint.

A number that represents the tradeoff between video quality and frame rate.

A smaller number implies that the MCU prioritizes sending quality video at the expense of a lower frame rate. A larger number implies that the MCU is prepared to send lower quality video at a higher frame rate.

The IP address and port to which RTCP (Real Time Control Protocol) packets are being received for the audio and video streams

A count of the number of "receiver report" type RTCP packets seen by the MCU.

A single RTCP packet may contain more than one report of more than one type. These are generally sent by any device receiving RTP (Real Time Protocol) media from the network and are used for auditing bandwidth, errors, and so on by the MCU.

Media packet loss reported by receiver reports sent to the MCU by the far end.

A count of the number of "sender report" type RTCP packets received by the MCU.

These are typically sent by any device that is sending RTP media.

A count of the number of reports seen by the MCU that are neither sender nor receiver reports.

The IP address and port to which the MCU is sending RTCP packets about this stream.

The number of packets sent.

The IP address and port to which RTCP (Real Time Control Protocol) packets are being sent for the audio and video streams.

A count of the number of "receiver report" type RTCP packets seen by the MCU.

A single RTCP packet may contain more than one report of more than one type. These are generally sent by any device receiving RTP (Real Time Protocol) media from the network and are used for auditing bandwidth, errors, and so on by the MCU.

A count of the reported packet loss on the control channel.

A count of the number of "sender report" type RTCP packets sent by the MCU.

These are typically sent by any device that is sending RTP media.

A count of the number of reports seen by the MCU that are neither sender nor receiver reports.

The IP address and port to which the MCU is sending RTCP packets about this stream.

The number of packets sent.

The number of fast update requests sent and received.

The number of flow control messages sent and received.

Enter the message to send to this participant.

Messages must be fewer than 256 characters, but depending on the viewing screen, messages at the higher-end of this limit might not display properly. So, consider limiting messages to about 180 characters. Messages longer than 256 characters will not be truncated; they will not display at all.

You can disable this setting from Settings > Conferences (see Conference settings).

The vertical position of the message on the conference display.

Choose from the top, middle, or bottom of the conference display.

Indicates how long the message appears on the endpoint's video screen.

The default setting is 30 seconds. To remove a message before it times out, click Clear message.

The name of the auto attendant

The number that you can dial to connect to the auto attendant

The status of an auto attendant with respect to its gatekeeper registration. The possible states are:

• n/a
  This auto attendant is not configured to be registered with the gatekeeper; because of this, there is no applicable registration status to show.
• Registering
  This auto attendant is in the process of registering with the gatekeeper.
• Deregistering
  The auto attendant is in the process of unregistering with the gatekeeper. This might occur if:
  • Gatekeeper registration has been turned off (either for that auto attendant only or for the entire MCU)
  • The configured gatekeeper has just been changed and the MCU is in the process of unregistering from the previous gatekeeper before registering its auto attendants with the new one.
• Re-registration pending / Retry timeout
  If the MCU fails to register an auto attendant with the gatekeeper, it enters these states temporarily before re-attempting the registration.
• <number> registered
  The auto attendant has been registered successfully with the gatekeeper and can be contacted using the number indicated.

For tips on configuring gatekeepers, see H.323 g atekeeper settings.

The status of an auto attendant with respect to its SIP registration. The possible states are:

• n/a
  This auto attendant is not configured to be registered with the SIP registrar; because of this, there is no applicable registration status to show.
• Registering
  This auto attendant is in the process of registering with the SIP registrar.
• Deregistering
  The auto attendant is in the process of unregistering with the SIP registrar. This might occur if:
  • SIP registration has been turned off (either for that auto attendant only or for the entire MCU)
  • The configured SIP registrar has just been changed and the MCU is in the process of unregistering from the previous SIP registrar before registering its auto attendants with the new one.
• Re-registration pending / Retry timeout
  If the MCU fails to register an auto attendant with the SIP registrar, it enters these states temporarily before re-attempting the registration.
• <number> registered
  The auto attendant has been registered successfully with the SIP registrar and can be contacted using the number indicated.

For tips on configuring SIP, see SIP settings.

Whether a PIN has been configured to restrict access to the auto attendant

The total number of calls received by the auto attendant since the last restart

A thumbnail of the custom banner, if one has been specified

The name of the auto attendant.

The number with which to register the auto attendant on the gatekeeper and/or SIP registrar.

See Configuring H.323 gatekeeper settings and SIP settings for details.

Select H.323 gatekeeper if you want the Numeric ID to be registered with the H.323 gatekeeper; select SIP registrar if you want the Numeric ID registered with the SIP registrar.

Note that for SIP, you must configure the ID with the SIP registrar for the MCU to be able to register that ID.

Assigns a password to the auto attendant.

If you set a PIN, all participants using the auto attendant will be required to enter this password.

Verifies the password.

If Enabled, displays the Create new conference option on the auto attendant so that the participant can create new ad hoc conferences using the auto attendant.

If disabled, participants will not be able to create new conferences from the auto attendant.

Note that this option will not be available if you have enabled Media port reservation on the Settings > Conferences page. When using port reservation mode, there can be no ad hoc conferences. For more information about port reservation, refer to Reservation of MCU media ports.

If Enabled, displays ad hoc conferences as well as scheduled conferences as options on the auto attendant.

If disabled, participants can only view scheduled conferences; ad hoc conferences will not be shown.

Note that this option will not be available if you have enabled Media port reservation on the Settings > Conferences page. When using port reservation mode, there can be no ad hoc conferences. For more information about port reservation, refer to Reservation of MCU media ports.

Enables all auto attendant participants to join any conferences scheduled to start while they are using the auto attendant.

If you select All scheduled conferences, this does not include conferences configured as private.

Choose the conferences to list on the auto attendant by selecting check boxes.

Note that even conferences that have been configured as private conferences will appear on this list. So as the admin user, you can enable private conferences to appear on an auto attendant. If you leave the conference unselected, it will not appear on the auto attendant.

Chooses the default TANDBERG Codian MCU graphic to use for your banner.

The custom banner identified for this auto attendant. Click Remove banner to remove this graphic as the banner. Click Update after uploading a new graphic.

Nothing displays here until you upload the custom graphic as described below.

The custom graphic to be used for a banner. Click Browse to locate the file on your hard drive.

The image file can be a JPEG, GIF or Windows BMP format with a maximum size of 352 x 64 pixels.

Sets a custom background color. Enter the color values in each field. Click Upload new file to display.

The background color is used if the banner is smaller than 352 x 64 pixels.

The name of the endpoint.

The IP address, host name, H.323 ID, E.164 number, or SIP URI of the endpoint.

Whether it is an H.323, SIP, or VNC endpoint.

The name of the endpoint.

The IP address, host name, or an E.164 address (phone number).

You can configure this endpoint as needing to be reached via an H.323 gateway without that gateway being already configured on the MCU. To do this, set this field to be <gateway address>!<E.164>.

The gateway through which the endpoint connects.

To configure a gateway on the MCU, go to Gateways. For more information, refer to Adding and updating gateways.

The DTMF sequence to be sent to an audio conferencing bridge.

Allows the MCU to send DTMF tones to an audio bridge after the audio bridge has answered the call. In this way, the MCU can navigate audio menus. This is useful where a conference on the MCU dials out to an audio-only conference on an audio bridge.

You can configure an audio bridge with a DTMF sequence as a pre-configured endpoint (either H.323 or SIP) which can then be added to any conference. Alternatively, you can add the audio bridge to an individual conference as a participant. You must specify the DTMF sequence in the Call-out parameters for that endpoint. The DTMF sequence can include digits 0-9 and * and #. There is a two second pause after the call connects after which the MCU will send the DTMF tones which are sent one every half second. You can insert as many additional two second pauses as you want by inserting commas into the DTMF sequence. Each comma represents a two second pause.

For example, you want the MCU to dial out to a PIN-protected audio conference on an audio bridge. The conference ID is 555 and the PIN is 888. The audio bridge requires that you press # after entering the ID and after entering the PIN. In this example the DTMF sequence is: 555#,,888#. The two commas represent a four second pause which allows the audio bridge's automated menu system time to process the ID and request the PIN.

These fields are used to identify incoming calls as being from the endpoint:

• Name: This must be the name that the endpoint sends to the MCU
• IP address: The IP address of the endpoint
• E.164: The E.164 number with which the endpoint is registered with the gatekeeper

The endpoint is recognized if all filled-in fields in this section are matched. Fields left blank are not considered in the match.

When you configure Call-in match parameters, an endpoint will be recognized as this pre-configured endpoint and the Conferencing parameters will be applied to a call from this endpoint.

The name that will be displayed in a conference as a label for this endpoint.

The name you enter here will override any default name configured on the endpoint. It will also override any other default name that might appear for an endpoint. For example, an endpoint's default name can be the name of the gateway through which the call was placed, or if the endpoint is called-in via a gatekeeper, its E.164 number.

Note that once an endpoint has connected, you cannot change the display name.

Select whether to use the unit-wide setting for motion/sharpness trade off, or configure an individual setting for use with this endpoint. Select from:

• <use box-wide setting>: this is the default value. In this case, the connection to the endpoint will use the motion / sharpness tradeoff setting from the Settings > Conferences page.
• 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 this endpoint.

Select the setting for transmitted video resolutions from the MCU to this endpoint. This setting overrides the unit-wide setting on the Settings > Conferences page

Retain the default setting (use box-wide setting) unless you are experiencing problems with the display of certain resolutions by this endpoint.

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. Therefore, you might want to use this setting to restrict the resolutions available to the MCU for transmissions to this endpoint.

Whether this endpoint is permitted to contribute the conference content channel. Select from:

<use conference default>: this endpoint will use the Content contribution from endpoints setting from the per-conference configuration.

Enabled: This endpoint is allowed to contribute the content channel, even if content contribution from endpoints is disabled in the per-conference configuration.

Disabled: This endpoint is not allowed to contribute the conference channel, even if content contribution from endpoints is enabled in the per-conference configuration.

This setting is provided to allow you to individually configure whether or not an endpoint is allowed to contribute content to a conference.

To use the content channel, the Content status must be enabled at the unit-wide level (on the Settings > Content page) and for any given conference Content channel video must also be enabled in the per-conference configuration.

Whether this endpoint is allowed to receive a separate content stream when in a conference.

This setting is provided to allow you to individually configure whether or not an endpoint is allowed to receive content from a conference.

To use the content channel, the Content status must be enabled at the unit-wide level (on the Settings > Content page) and for any given conference Content channel video must also be enabled in the per-conference configuration.

Select a border size for video transmitted to this endpoint.

This sets a border thickness to display around the video image. This is useful where the image is displaying off the edges of the participant's screen; use a border to force the image to display properly.

Applying a border size here means that this border size will always be used for this endpoint's transmitted video. Note that you can also apply a border to a participant in a conference from the Conference list > Conference > Participant's display page.

Sets the layout family to be used when calling out to this endpoint.

If this is set to Use box-wide setting then the default view family that has been configured via the Conference settings page will be used.

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

These settings take priority over the Default bandwidth from MCU setting configured in the global Conference settings (see Conference settings).

The maximum combined media bandwidth advertised by the MCU to endpoints.

These settings take priority over the Default bandwidth to MCU setting configured in the global Conference settings (see Conference settings).

• use conference configuration: the setting for Layout control via FECC / DTMF will be determined by the configuration of the conference
• Disabled: the participant using this endpoint will not be allowed to change their view layout using either FECC or DTMF
• FECC only: the participant using this endpoint will be allowed to change their view layout using FECC
• FECC with DTMF fallback: the participant using this endpoint will be allowed to change their view layout using FECC. If FECC is not available, this participant will be able to use DTMF

This setting takes precedence over the per-conference layout control setting for conferences into which the endpoint is invited.

Use this option to mute in-band DTMF from this endpoint. Choose from:

• use conference configuration: the setting for Mute in-band DTMF will be determined by the configuration of the conference
• Never: the in-band DTMF from this endpoint will never be muted. Any DTMF tones sent from this endpoint will be audible to conference participants
• Always: the in-band DTMF from this endpoint will always be muted. Any DTMF tones sent from this endpoint will not be audible to conference participants
• When used for MCU control: if a participant is using in-band DTMF to control conference layout and for other in-conference features, the tones will be muted and will not be audible to conference participants. The MCU will only expect a participant to use DTMF for MCU control if Layout control via FECC / DTMF is set to FECC with DTMF fallback and FECC is unavailable to the endpoint.

In some scenarios, where a conference is cascaded onto an audio bridge, it might be useful for one of the participants in that conference to be able to send in-band DTMF to the MCU. This is for the purposes of sending the conference ID or PIN to the audio conferencing bridge. In this case, the Mute in-band DTMF setting for the endpoint of that participant needs to be Never. However, you can instead send DTMF tones to the audio conferencing bridge directly from the MCU; for more information refer to Sending DTMF to an audio bridge.

Unless you need to configure a particular setting for this endpoint, set this to use conference configuration and ensure you have the Mute in-band DTMF setting as required in the conference configuration (see Adding and updating conferences).

This setting takes precedence over the per-conference Mute in-band DTMF setting for conferences into which the endpoint is invited.

Set the initial audio status of an endpoint to be either active or muted.

If set to muted, when the endpoint joins a conference, it will not be able to contribute audio to the conference. For example, you can mute audio from an endpoint if somebody wants to be seen in the conference, but does not want to contribute verbally. You can mute both audio and video if required. This can be altered during the course of the conference by going to Conferences and clicking on the name of a conference and altering this participant's settings.

Set the initial video status of an endpoint to be either active or muted.

If set to muted, when the endpoint joins a conference, it will not be able to contribute video to the conference. For example, you can mute video from an endpoint if somebody wants to see the conference, but not be seen themselves. You can mute both audio and video if required. This can be altered during the course of the conference by going to Conferences and clicking on the name of a conference and altering this participant's settings.

When a participant disconnects from a conference and only endpoints set to Automatic disconnection are left, all those participants are disconnected.

Set to enabled if you want this endpoint to be automatically disconnected from conferences when only endpoints set to Automatic disconnection remain in a conference when any other participant has disconnected.

Note that this setting is useful where you have configured a TANDBERG Codian IP VCR as an endpoint so that the IP VCR can be automatically called into a conference to record the session. In this case, the IP VCR will stop recording when the conference ends (that is, when everyone has left the conference). For more information about using the IP VCR in this way, refer to the IP VCR online help.

Can be used to ensure only specific codecs are permitted on calls to (and received from) this endpoint.

If Enabled, you can select which codecs are allowed to be used when communicating with this endpoint. When enabled this setting overrides the unit-wide codec selection on the Settings > Conference page.

The name of the endpoint.

The IP address, host name, directory number, or SIP URI (in the format 1234@codian.com).

The address of the SIP endpoint can be a directory number if you are using a SIP registrar.

Allows calls to this endpoint to use a directory number (in the Address field) and the SIP registrar.

If you have this enabled, you must configure the SIP registrar on the Settings > SIP page.

Select the protocol to be used for call control messages for outgoing call connections to this endpoint.

If you want this endpoint to use the unit-wide outgoing transport setting, select box-wide default transport. If this endpoint uses TCP, select TCP as the outgoing transport. If this endpoint uses UDP, select UDP as the outgoing transport. If this endpoint uses TLS, select TLS. Note that if you want the MCU to use TLS for call setup, you must have the encryption feature key (or the Secure management feature key) and the TLS service must be enabled on the Network > Services page.

Using TLS for call setup is not sufficient for the call to be considered encrypted such that it can participate in a conference which requires encryption. Where encryption is required in the conference configuration, a SIP call must use SRTP. For more information about SIP encryption, refer to Configuring encryption settings.

This setting overrides the unit-wide setting for Outgoing transport on the Settings > SIP page. For more information about configuring SIP, refer to Configuring SIP settings.

The DTMF sequence to be sent to the audio conferencing bridge.

Allows the MCU to send DTMF tones to an audio bridge after the audio bridge has answered the call. In this way, the MCU can navigate audio menus. This is useful where a conference on the MCU dials out to an audio-only conference on an audio bridge.

You can configure an audio bridge with a DTMF sequence as a pre-configured endpoint (either H.323 or SIP) which can then be added to any conference. Alternatively, you can add the audio bridge to an individual conference as a participant. You must specify the DTMF sequence in the Call-out parameters for that endpoint. The DTMF sequence can include digits 0-9 and * and #. There is a two second pause after the call connects after which the MCU will send the DTMF tones which are sent one every half second. You can insert as many additional two second pauses as you want by inserting commas into the DTMF sequence. Each comma represents a two second pause.

For example, you want the MCU to dial out to a PIN-protected audio conference on an audio bridge. The conference ID is 555 and the PIN is 888. The audio bridge requires that you press # after entering the ID and after entering the PIN. In this example the DTMF sequence is: 555#,,888#. The two commas represent a four second pause which allows the audio bridge's automated menu system time to process the ID and request the PIN.

These fields are used to identify incoming calls as being from the endpoint:

• Username: This must be the username that the endpoint sends to the MCU
• IP address: The IP address of the endpoint

The endpoint is recognized if all filled-in fields in this section are matched. Fields left blank are not considered in the match.

Note that in some cases a SIP registrar can cause a call to appear to come from the IP address of the registrar rather than the IP address of the endpoint. In this case, to use call-in match parameters, leave the IP address field blank and enter the correct username. The call will be matched by username.

When using LCS, the username that will be matched is the user's display name (e.g. Peter Rabbit) rather than the sign-in name (bluecoat@codian.com).

The name that will be displayed in a conference as a label for this endpoint.

The name you enter here will override any default name configured on the endpoint. It will also override any other default name that might appear for an endpoint. For example, an endpoint's default name can be the name of the gateway through which the call was placed, or if the endpoint is called-in via a gatekeeper, its E.164 number.

Note that once an endpoint has connected, you cannot change the display name.

Choose whether to use the box-wide setting for motion/sharpness trade off, or configure an individual setting for this endpoint. Select from:

• Use box-wide setting: this is the default value. In this case, the endpoint will use the motion/sharpness tradeoff setting from the Settings > Conferences page
• 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 this endpoint.

Choose the setting for transmitted video resolutions from the MCU to this endpoint. This setting overrides the unit-wide setting on the Settings > Conferences page.

Retain the default setting (use box-wide setting) unless you are experiencing problems with the display of certain resolutions by this endpoint.

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. Therefore, you might want to use this setting to restrict the resolutions available to the MCU for transmissions to this endpoint.

Whether this endpoint is permitted to contribute the conference content channel. Select from:

<use conference default>: this endpoint will use the Content contribution from endpoints setting from the per-conference configuration.

Enabled: This endpoint is allowed to contribute the content channel, even if content contribution from endpoints is disabled in the per-conference configuration.

Disabled: This endpoint is not allowed to contribute the conference channel, even if content contribution from endpoints is enabled in the per-conference configuration.

This setting is provided to allow you to individually configure whether or not an endpoint is allowed to contribute content to a conference.

To use the content channel, the Content status must be enabled at the unit-wide level (on the Settings > Content page) and for any given conference Content channel video must also be enabled in the per-conference configuration.

Currently, all content is sent to SIP endpoints in the main video channel.

Choose a border size for video transmitted to this endpoint.

This sets a border thickness to display around the video image. This is useful where the image is displaying off the edges of the participant's screen; use a border to force the image to display properly.

Applying a border size here means that this border size will always be used for this endpoint's transmitted video. Note that you can also apply a border to a participant in a conference from the Conference list > Conference > Participant's display page.

Sets the layout family to be used when calling out to this endpoint.

If this is set to Use box-wide setting then the default view family that has been configured via the Conference settings page will be used.

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

These settings take priority over the Default bandwidth from MCU setting configured in the global Conference settings (see Conference settings).

The maximum combined media bandwidth advertised by the MCU to endpoints.

These settings take priority over the Default bandwidth to MCU setting configured in the global Conference settings (see Conference settings).

• use conference configuration: the setting for Layout control via FECC / DTMF will be determined by the configuration of the conference
• Disabled: the participant using this endpoint will not be allowed to change their view layout using either FECC or DTMF
• FECC only: the participant using this endpoint will be allowed to change their view layout using FECC
• FECC with DTMF fallback: the participant using this endpoint will be allowed to change their view layout using FECC. If FECC is not available, this participant will be able to use DTMF

This setting takes precedence over the per-conference layout control setting for conferences into which the endpoint is invited.

Use this option to mute in-band DTMF from this endpoint. Choose from:

• use conference configuration: the setting for Mute in-band DTMF will be determined by the configuration of the conference
• Never: the in-band DTMF from this endpoint will never be muted. Any DTMF tones sent from this endpoint will be audible to conference participants
• Always: the in-band DTMF from this endpoint will always be muted. Any DTMF tones sent from this endpoint will not be audible to conference participants
• When used for MCU control: if a participant is using in-band DTMF to control conference layout and for other in-conference features, the tones will be muted and will not be audible to conference participants. The MCU will only expect a participant to use DTMF for MCU control if Layout control via FECC / DTMF is set to FECC with DTMF fallback and FECC is unavailable to the endpoint.

In some scenarios, where a conference is cascaded onto an audio bridge, it might be useful for one of the participants in that conference to be able to send in-band DTMF to the MCU. This is for the purposes of sending the conference ID or PIN to the audio conferencing bridge. In this case, the Mute in-band DTMF setting for the endpoint of that participant needs to be Never. However, you can instead send DTMF tones to the audio conferencing bridge directly from the MCU; for more information refer to Sending DTMF to an audio bridge.

Unless you need to configure a particular setting for this endpoint, set this to use conference configuration and ensure you have the Mute in-band DTMF setting as required in the conference configuration (see Adding and updating conferences).

This setting takes precedence over the per-conference Mute in-band DTMF setting for conferences into which the endpoint is invited.

Set the initial audio status of an endpoint to be either active or muted.

If set to muted, when the endpoint joins a conference, it will not be able to contribute audio to the conference. For example, you can mute audio from an endpoint if somebody wants to be seen in the conference, but does not want to contribute verbally. You can mute both audio and video if required. This can be altered during the course of the conference by going to Conferences and clicking on the name of a conference and altering this participant's settings.

Set the initial video status of an endpoint to be either active or muted.

If set to muted, when the endpoint joins a conference, it will not be able to contribute video to the conference. For example, you can mute video from an endpoint if somebody wants to see the conference, but not be seen themselves. You can mute both audio and video if required. This can be altered during the course of the conference by going to Conferences and clicking on the name of a conference and altering this participant's settings.

When a participant disconnects from a conference and only endpoints set to Automatic disconnection are left, all those participants are disconnected.

Set to enabled if you want this endpoint to be automatically disconnected from conferences when only endpoints set to Automatic disconnection remain in a conference when any other participant has disconnected.

Can be used to ensure only specific codecs are permitted on calls to (and received from) this endpoint.

If Enabled, you can choose which codecs are allowed to be used when communicating with this endpoint. When enabled, this setting overrides the unit-wide codec selection on the Settings > Conference page.

The name of the computer used for the VNC application (VNC endpoint).

The IP address or host name of the computer used for the VNC application (VNC endpoint).

The port used for communication to the VNC endpoint.

The VNC server password for the computer you're trying to view.

Re-enter the VNC password.

When a participant disconnects from a conference and only endpoints set to Automatic disconnection are left, all those participants are disconnected.

Set to enabled if you want this endpoint to be automatically disconnected from conferences when only endpoints set to Automatic disconnection remain in a conference when any other participant has disconnected.

The descriptive name of the gateway.

The IP address or host name of the gateway.

The configured preferred bandwidth to the MCU from the gateway, or <default value> if no preference has been specified.

The configured preferred bandwidth from the MCU to the gateway, or <default value> if no preference has been specified.

The descriptive name of the gateway.

All gateways must have a unique name.

The IP address or host name of the gateway.

Choose whether to use the unit-wide setting for motion/sharpness trade off, or configure an individual setting for this gateway. Choose from:

• Use unit-wide setting: this is the default value. In this case, connections to the gateway will use the motion/sharpness tradeoff setting from the Settings > Connections page
• 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 this endpoint.

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

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

Enables or disables the built-in gatekeeper.

To use the built-in gatekeeper, you must enable it here.

Enter the IP address(es), or hostname(s) (or <host>:<port number> to specify a port other than the default of 1719 on the neighboring gatekeeper), of the neighboring gatekeeper(s).

These are the gatekeepers to which the built-in gatekeeper will send an LRQ if it has received an ARQ to resolve an ID which it does not currently have registered. The built-in gatekeeper will then use the information received from the neighbor(s) to reply to the original request.

Configures the built-in gatekeeper to reply to LRQs from other gatekeepers.

These requests can come from any gatekeeper which has the MCU's built-in gatekeeper configured as one of its neighbors.

Configures the built-in gatekeeper to send (or not to send) LRQs regarding unknown IDs to its neighbor(s). Choose from the options:

• Disabled: The MCU will only respond to LRQs about IDs registered with itself. It will not forward LRQs about IDs that are not registered with itself to neighboring gatekeepers.
• Enabled, using local return address: The MCU will put, in the LRQ, its own address as the return address for the LCF.
• Enabled, using received return address: The MCU will put, in the LRQ, the address of the gatekeeper that originated the request as the return address for the LCF. Use this option only if you are configuring the MCU to operate in an environment with a multiple-level gatekeeper hierarchy. For example, the 'received address' is required by the national gatekeepers connected to the Global Dialing Scheme (GDS).

Unless you have selected to Accept LRQs, you cannot configure the MCU to forward any LRQs.

Enabling using received return address can be a significant security risk. Only use this setting with proper cause.

This setting enables the built-in gatekeeper to accept LCF message responses from any IP address.

This setting is for use in environments with a multiple-level gatekeeper hierarchy. For example, this feature is required by the national gatekeepers connected to the Global Dialing Scheme (GDS).

Enabling this setting can be a significant security risk. Only use this setting with proper cause.

The ID which the registrant has registered with the gatekeeper.

IDs can be numbers, H.323 IDs or prefixes.

The type of registration.

One of: E.164 (digits), H.323 ID or Prefix .

This registrations index within the total number of registrations that this registrant has made with the gatekeeper.

In the format X / Y where Y is the number of registrations that this registrant has made with the built-in gatekeeper, and X is this particular registration's position within the total. Therefore, if a device registered 3 IDs with the gatekeeper and this was the second registration to be made, the Index would be 2 / 3.

The IP address of the device from which this registration was made.

If the remote device has indicated via the RAI (Resource Availability Indication) mechanism that it is close to its resource limit, the Registrant will be labeled as "almost out of resources".

The IP address of the device.

If the remote device has indicated via the RAI (Resource Availability Indication) mechanism that it is close to its resource limit, the Registrant will be labeled as "almost out of resources".

The registered H.323 ID of the device.

To help identify registering devices, if the registrant has registered a H.323 ID (which will typically be its device name) that H.323 ID is shown here. If the device has registered multiple H.323 IDs, only the first is displayed.

The number of registrations that this device has made with the built-in gatekeeper.

Click (view) to display individual registrations for the selected device. (The format is the same as the ID view, but the table only includes entries for one device.)

The time today or date and time of the last registration.

The MCU must have at least one configured user with administrator privileges. By default, the User ID is "admin" and no password is required.

If you configure the MCU with advanced account security mode, a password is required. For more information about advanced account security mode, refer to Configuring security settings.

After logging into the MCU for the first time (see Logging into the web interface), you can change the User ID and password for this account. The privilege level is fixed at administrator for the admin user - who can see all the pages and change settings.

The MCU must have at least one configured user with access privileges below administrator. The fixed User ID for this user is "guest" and by default no password is required.

If you configure the MCU with advanced account security mode, the guest account requires a password that adheres to secure password criteria. For more information about advanced account security mode, refer to Configuring security settings.

You cannot change the name of the "guest" User ID. You can add a password.

The main difference between an administrator and users with lower privilege levels is that administrators can change settings that affect all conferences and the configuration of the MCU itself, whereas other users only have access to individual conferences and to their own profiles.

Users with administrator access can:

• View MCU-wide status (Status)
• Access all settings pages (Settings)
• Perform software upgrades (Settings > Upgrade)
• Change system-wide conference settings (Settings > Conferences)
• View the Event log (Logs)
• Configure H.323 gateways (Gateways)
• Configure the built-in gatekeeper (Gatekeeper)
• Manage users (Users)
• Manage endpoints (Endpoints)
• Configure auto attendants (Conferences > Auto attendants)
• Fully control conferences (Conferences)

Users with this privilege level can:

• Change their own profile (Profile)
• View the list of active conferences (Conferences)
• View conferences via streaming (Conferences)
• View participant lists for active conferences (Conferences)
• Schedule new conferences (Conferences)
• Fully control and modify all public conferences and the conferences they own (Conferences)
• Configure H.323 gateways (Gateways)
• Manage endpoints (Endpoints)

Users with this privilege level can:

• Change their own profile (Profile)
• View the list of active conferences (Conferences)
• View conferences via streaming (Conferences)
• View participant lists for active conferences (Conferences)
• Schedule new conferences (Conferences)
• Fully control and modify conferences they own (Conferences)
• Exercise limited control of conferences owned by other users (Conferences)

See Conference ownership for additional information on which actions are permitted (and forbidden) by limited control.

Users with this privilege level can:

• Change their own profile (Profile)
• View the list of active conferences (Conferences)
• View conferences via streaming (Conferences)
• View participant lists for active conferences (Conferences)
• Schedule new conferences (Conferences)
• Fully control and modify conferences they own (Conferences)

Users with this privilege level can:

• Change their own profile (Profile)
• View the list of active conferences (Conferences)
• View conferences via streaming (Conferences)
• View participant lists for active conferences (Conferences)

Users with this privilege level can:

• Change their own profile (Profile)
• View the list of active conferences (Conferences)
• View conferences via streaming (Conferences)

Users with this privilege level can:

• Change their own profile (Profile)
• View the list of active conferences (Conferences)

The user name that the user needs to access the web interface of the MCU. Although you can enter text in whichever character set you require, note that some browsers and FTP clients do not support Unicode characters.

The full name of the user.

Access privileges associated with this user.

See User privileges for detailed explanations.

The associated E.164 telephone number.

The associated video endpoint.

The configured image to display for this user.

Identifies the log-in name that the user will use to access the MCU web interface.

Although you can enter text in whichever character set you require, note that some browsers and FTP clients do not support Unicode characters.

The full name of the user.

The required password, if any.

Although you can enter text in whichever character set you require, note that some browsers and FTP clients do not support Unicode characters.

In advanced account security mode (configured on the Settings > Security page), passwords must have:

• at least fifteen characters
• at least two uppercase alphabetic characters
• at least two lowercase alphabetic characters
• at least two numeric characters
• at least two non-alphanumeric (special) characters
• not more than two consecutive repeating characters. That is, two repeating characters are allowed, three are not

In advanced account security mode, a password must be different from the previous ten used with that account. Also, a password will expire if it is not changed within 60 days.

If the MCU is not using advanced account security mode, any password can be used.

Note that passwords are stored in the configuration.xml file as plain text unless the MCU is configured (or has ever been configured) to use advanced account security mode. For more information, refer to Configuring security settings.

Note that this field is only active when adding a new user. If you are updating an existing user and want to change that user's password, click Change password instead.

Verifies the required password.

Select to disable this account.

This can be useful if you want to keep an account's details, but do not want anyone to be able to use it at the moment.

You cannot disable the system-created admin account.

The system-created guest account is disabled by default. If you enable it, the MCU will create a security warning.

In advanced account security mode, a non-admin account will expire after 30 days of inactivity; that is, the MCU will disable it. To re-enable a disabled account, clear this option.

For more information about advanced account security mode, refer to Configuring security settings.

Prevents user from changing password.

This is useful where you want multiple users to be able to use the same user ID. The system-created guest account has Lock password enabled by default.

Select this option to force a user to change their password. Next time this user attempts to log in to the MCU, a change password prompt will appear.

This option is enabled by default for a newly created account. It is a good idea for new users to set their own secure passwords.

This option is not available for accounts where Lock password is selected.

When the user changes his password, the MCU clears this check box automatically.

The access privileges to be granted to this user.

See User privileges for detailed explanations.

Associates an E.164 telephone number with a user account.

If the MCU receives a call from the E.164 phone number provided, it matches the number to the user account. This allows the MCU to take the appropriate action if one (or both) of the following fields are completed.

Associates a configured endpoint with the user. This is used when a participant's video stream is from a separate device such as a web camera on a PC or a recording from a TANDBERG Codian IP VCR.

If you set an associated video endpoint for a user, when a call is received from the E.164 phone number, the MCU knows that that call is audio-only. To provide the user with a video stream, the MCU calls the endpoint entered in this field. The user then has the complete conference experience with the audio on the telephone and a separate video stream for example on a computer with a web camera installed. The audio and video steams are matched so that the layout views for all participants reflect the level of audio received on the call from the E.164 phone number.

Do not set the user's E.164 phone number and Associated video endpoint as the same number. If a user is going to be a normal video endpoint user, simply enter the E.164 phone number and leave the associated video endpoint field set to None.

If required, a user's video contribution can be a recording on a TANDBERG Codian IP VCR. In this case the recording must first be configured as an H.323 endpoint on the MCU.

See Adding an H.323 endpoint for information about adding endpoints.

The image to be used if a user joins a conference as an audio-only participant calling from the E.164 phone number specified above and there is no Associated video endpoint.

This option is only available after you add the user.

Because there is no video stream for the user, you can display a still image in the pane where the participant would normally appear.

The maximum size of the picture is 176 x 144 pixels and the maximum file size is 500k.

Click Browse to locate the image (jpg, gif, or Windows bmp file). Then, click Send file to upload the image to the MCU.

The bitmap will only display if the user calls in to the MCU from the E.164 phone number using an audio-only device and there is no associated video endpoint.

Your name, which identifies you to other users.

Changing this field does not change your log-in User ID.

Associates an E.164 telephone number with your user account.

This limits the setup you will need to do each time you join a video conference. When the MCU receives a call from this number, it will be recognized as coming from your phone. If the device is an audio-only phone, you can set up an associated video endpoint and/or upload a picture file.

This field is not available for the system admin account.

Associates a configured H.323 endpoint with your user account.

If you call in to the MCU from your E.164 phone number using an audio-only device, the MCU calls your associated video endpoint and sends the conference video stream to that associated video endpoint (and receives a video-only stream from that endpoint).

This field is not available for the system admin account.

Type your current password.

Type your new password.

In advanced account security mode, passwords must have:

• at least fifteen characters
• at least two uppercase alphabetic characters
• at least two lowercase alphabetic characters
• at least two numeric characters
• at least two non-alphanumeric (special) characters
• not more than two consecutive repeating characters. That is, two repeating characters are allowed, three are not

In advanced account security mode, a new password must be different to the previous 10 passwords that have been used with an account.

Verify your new password.

You can upload an image which will display in the conference when you join conferences in audio-mode only.

Click Browse to locate the bitmap image. Then, click Send file to upload the image to the MCU.

The bitmap will only display if you call in to the MCU from your E.164 phone number using an audio-only device and you do not have an associated video endpoint.

Identifies the greatest video size that the MCU will send and receive when connected to a video endpoint.

This option is only available if the MCU 4CIF (HRO) feature key is present.

Choose the unit-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 unit-wide setting for calls to/from that endpoint.

Choose the unit-wide 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).

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:
  This icon is also visible to participants of an encrypted conference if there are people streaming that conference.
• 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 a TANDBERG Codian 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, or the participant has muted their endpoint's video channel to the MCU.
• Streaming participants: an icon appears in the top left of the conference display to indicate if there are any streaming participants in the conference. If enabled, the icon will only display if there are one or more streaming participants. Streaming participants are people who are viewing and listening to the conference using a web browser.
• 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.

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>

If you want streaming viewers to see the welcome message, you must configure the duration as 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 unit-wide 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 unit-wide setting for calls from that endpoint.

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

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 unit-wide 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 video data to the MCU.

Note that the Custom codec selection setting for an individual endpoint will override this unit-wide setting for calls from that endpoint.

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 of 30, for example: 15fps)
• PAL
  The MCU will transmit video at 25 frames per second (or a fraction of 25, for example: 12.5fps)

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).

Typically, you only need to set this value to lower than the default (1400 bytes) if there was a known packet size restriction in the path between the MCU and potential connected endpoints.

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 TANDBERG 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.

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.

Select the delay to be applied to audio relative to video.

A setting used only to rectify some types of 'lip sync' issues sometimes found with certain endpoints. Leave at default setting, unless advised to alter it by TANDBERG customer support or a reseller.

Controls whether connected endpoints are allowed to use floor and chair control operations.

This option acts as a unit-wide control over whether any H.243 floor and chair control operations are permitted. Individual conferences may have their own floor and chair control policies set; however, if this setting is Disabled then no floor or chair control operations will be possible within conferences. Changing this setting will only affect new calls - existing calls will continue with the setting in force when they became active.

For more information, refer to H.243 floor and chair control.

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 wish callers to be able to create conferences in this way, select one of the other options.

Determines the redial options for failed preconfigured participants.

Controls the frequency of redial attempts to preconfigured participants. The options are:

• Never redial
  The MCU will never attempt to redial a preconfigured participant, even if they fail to connect.
• Default
  The MCU will make nine retry attempts to a preconfigured participant who fails to connect. The first four will be at one minute intervals, the following five will be at five minute intervals.
• Constant redial
  The MCU will make constant retry attempts to a preconfigured participant who fails to connect. The first four will be at one minute intervals, all redial attempts after this will be at five minutes.

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 wish 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 wish 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.
• 5 seconds, 10 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.

Enables the MCU to use an H.323 gatekeeper for registration of numeric identifiers for its conferences and/or auto attendants.

When set to Disabled then no gatekeeper registrations are attempted (and existing registrations are torn down), regardless of other gatekeeper or per-conference settings.

When set to Enabled registrations with the gatekeeper are attempted, and the gatekeeper is contacted for incoming and outgoing calls. If the gatekeeper does not respond, calls are still connected if possible. When set to Required registrations with the gatekeeper are attempted but calls are not connected if the gatekeeper cannot be contacted.

Identifies the network address of the gatekeeper to which MCU registrations should be made.

This can be specified either as a host name or as an IP address.

This field will have no effect if H.323 Gatekeeper usage (see above) is set to Disabled.

The gatekeeper can be either the built-in gatekeeper enabled on the Gatekeeper page (see Displaying the built-in gatekeeper registration list) or an external gatekeeper. To use the built-in gatekeeper enter "127.0.0.1". For an external gatekeeper, enter its host name or IP address.

Controls how the MCU identifies itself when registering with its configured gatekeeper.

TANDBERG recommends that you use the Terminal / gateway option unless you are using a service prefix (in this case, use Gateway). Only use a different option if you are:

• having specific problems
• using the TANDBERG VCS Gatekeeper (with or without a service prefix), in which case use MCU (standard)
• using the Cisco Gatekeeper (with or without a service prefix), in which case use Gateway (Cisco GK compatible)
• using the VCON MXM Gatekeeper (with or without a service prefix), in which case use MCU (compatible)

Refer to the Knowledge Base in the Support section of the web site for more details about interoperability with gatekeepers.

Whether a call involves consultation with the configured gatekeeper also depends on the Port A and Port B settings. For all incoming calls, and outgoing calls dialed by address rather than by E.164 phone number, the gatekeeper will be used to validate the connection only if the network port over which the connection is made is selected here.

Specifies an identifier that the MCU can use to register itself with the H.323 gatekeeper.

Before the MCU can register any IDs with the H.323 gatekeeper, it must make a unit-wide registration.

This field is required for the gatekeeper registration.

This will have no effect if H.323 gatekeeper usage is disabled.

If the configured gatekeeper required password authentication from registrants, select the Use password check box and type the password.

Note that where password authentication is used, the (Mandatory) H.323 ID to register will be used as the username.

Specifies an optional group of digits that are added to the beginning of each conference or auto attendant's numeric identifier before registering it with the H.323 gatekeeper.

Conferences and auto attendants registered with a gatekeeper have a numeric identifier. The numeric identifier is a unique sequence of digits entered from a video-conferencing endpoint to connect directly to the conference or auto attendant. This eliminates the need for users to navigate additional menus or to know the IP address of the MCU.

To usefully partition the dialing space, you might need to ensure that all registrations from a single MCU start with the same sequence of digits.

Using registration prefixes also can benefit large-scale dial plan changes. For example, you can change all MCU registrations to begin with "121" instead of "11" by changing a single MCU configuration field rather than individually amending every conference or auto attendant's associated numeric identifier.

If H.323 gatekeeper usage is disabled, this field will have no effect.

Note that if you are also intending to use the MCU service prefix (see below), TANDBERG recommends that you set both prefixes to the same number.

If required, specify a group of digits which the H.323 gatekeeper may use to identify calls to be routed to the MCU.

This field is optional. If set, users dialing any number beginning with this prefix will have their call directed to the MCU. This might be useful if you wish to create conferences in response to unknown E.164 numbers.

Any numbers following the prefix will be identified by the MCU as a conference or auto attendant number. For example, if a conference has Numeric ID "3333" and you have set the service prefix to be "121", then a user dialing "1213333" will be connected to that conference.

This field will have no effect if H.323 gatekeeper usage is disabled.

Note that if you are also intending to use the Prefix for MCU registrations (see above), TANDBERG recommends that you set both prefixes to the same number.

If the MCU is unable to match a call to a conference or auto attendant, the action for Incoming calls to unknown E.164 number will be applied. This is a setting on the Settings > Conferences page (see Configuring global conference settings). This action can be set to Create new ad hoc conference.

This setting controls whether conferences' configured numeric IDs are allowed to be registered with the gatekeeper.

This setting is the global control that allows or disallows conferences to be registered with the gatekeeper.

Individual conferences will be registered or not depending on the per-conference Numeric ID registration setting which is on the Add conference page for scheduled conferences and for ad hoc conferences it is in the ad hoc conference template.

This would normally be Enabled; by setting it to Disabled, an administrator can prevent users from adding to the set of IDs registered with the configured gatekeeper, even if those users enable the gatekeeper Numeric ID registration setting for conferences they control. This may be desired when working with certain types of H.323 gatekeeper whose behavior in some modes is to disconnect active calls when the set of registered IDs changes.

This setting affects both the registration of numeric IDs configured for scheduled conferences and the registration of ad hoc conferences.

This field will have no effect if H.323 Gatekeeper usage is set to Disabled.

Select this option if you want the MCU to inform the gatekeeper about its availability or non-availability. This information will be used by the gatekeeper when it is selecting where to place ad hoc conferences.

Only use this option where multiple MCUs are registered with the same MCU service prefix on the same gatekeeper.

If you select this option, you must configure the thresholds for conferences and/or video ports.

Thresholds:

• Conferences: Enter any number of conferences between 0 and 200. (A value of 0 will mean that the MCU will always indicate 'unavailable'.)
• Video ports: Enter a number between 0 and the number of video ports on your MCU; for example, on an MCU 4205, there are 12 video ports, so enter a number between 0 and 12. (A value of 0 will mean that the MCU will always indicate 'unavailable'.)

The ability of the MCU to send resource availability messages is useful in a network where there are multiple MCUs or where there are several media blades in an MSE.

In an environment with multiple conferencing devices registered with the same gatekeeper, that gatekeeper should favor devices in the available state when choosing where to place new calls.

For example, when one MCU sends the gatekeeper a message indicating that it is not available, the gatekeeper will then attempt to use a different MCU for new ad hoc conferences.

Resource availability indications are most useful where the thresholds are configured such that the MCU informs the gatekeeper that it is unavailable when its resources are nearly used up.

Conferences without any active participants do not contribute to the conference count; any video port in use is added to the video port count.

When either threshold is equaled or exceeded, the MCU sends a message to indicate that it is not available; when the resource usage drops such that neither threshold is equaled or exceeded, the MCU sends a message indicating that it is available.

You might choose to only configure one of the thresholds. You are probably aware of how your video conferencing resources tend to be used by participants and you need to consider this when configuring the thresholds. For example, you could have four people who have each started an ad hoc conference; you might know that it is usual for such conferences to end up having ten participants. In this case, on a 40-port MCU you could set the conference threshold to 4 to indicate that it will be out-of-resources very soon. On the same MCU if you set the video port threshold to 35 and left the conference threshold empty, another four or more people could begin ad hoc conferences on this MCU before the participants expected in the original four conferences had dialed in.

Displays the IP address of the gatekeeper currently being used by the MCU.

This information might be useful if the gatekeeper has been specified with a host name rather than with an IP address.

If the MCU has been unable to reach the configured gatekeeper and has instead registered with an alternate gatekeeper, the status displayed here will be "registered with alternate gatekeeper <IP address>".

Displays the local IP address and port number that the MCU has registered with the gatekeeper.

This information might be useful if the MCU has more than one IP address, for instance if both Ethernet interfaces are in use.

Displays the number of 'alternate' gatekeepers configured on the H.323 gatekeeper. This figure comes from the gatekeeper itself; if there are any 'alternate' gatekeepers configured, the gatekeeper tells the MCU their IP addresses.

Where the configured gatekeeper has told the MCU about any configured 'alternate' gatekeepers and if the MCU loses contact with the configured gatekeeper, the MCU will attempt to register with each of the 'alternates' in turn. If none of the 'alternate' gatekeepers responds, the MCU will report that the registration has failed.

If the MCU successfully registers with an 'alternate' gatekeeper:

• the H.323 gatekeeper status will indicate that registration is with an 'alternate'
• the list of 'alternates' received from the new gatekeeper will replace the previous list
• the MCU will only revert back to the original gatekeeper if the 'alternate' fails and only if the original gatekeeper is configured as an 'alternate' on the current gatekeeper's list of 'alternates'

Note that if the MCU registers with an 'alternate' that does not itself supply a list of 'alternates', the MCU will retain the original list and if it loses contact with the current gatekeeper, each one will be attempted from the top again as before.

Displays whether the gatekeeper is configured to send resource availability indications and if it is, it displays the current state of the resource availability status of the MCU.

The possible statuses are:

• resources available
• resources unavailable
• <indications not configured>
  

Displays the number of E.164 numbers plus H.323 IDs plus prefixes that the MCU has registered with the gatekeeper.

It also shows how many registrations are in progress but are not fully registered yet.

Full information on the gatekeeper registrations being made by the MCU can be seen by clicking on details; this takes you to the Active registrations page.

Displays the identifier that the MCU has used to register itself with the H.323 gatekeeper.

For more information about the H.323 ID, refer to the table above.

Displays the identifier that the gatekeeper has registered for calls to be routed to the MCU.

For more information about this prefix, refer to the table above.

Type the ID, or a part of the ID for which you want to see details.

The filtered registration list is automatically updated when you change the ID and name filters.

Applying a filter will filter all registrations and display any that match, even if those registrations are not on the page currently displayed.

Type the text, or a part of the text that will appear in the "Details" column of the Registrations table. For example, type 'Conference' to filter the registrations to show all conferences that the MCU is attempting to register with the gatekeeper.

Enables the MCU to use a SIP registrar for registrations of numeric identifiers for its conferences and/or auto attendants.

When set to Disabled then no SIP registrar registrations are attempted (and existing registrations are torn down), regardless of other per-conference settings.

When set to Enabled registrations with the registrar are attempted, and calls can be made through the registrar. Note that 'Use SIP registrar' must be Enabled when adding a participant.

Identifies the network address of the SIP registrar to which MCU registrations should be made.

This can be specified either as a host name or as an IP address. This field will have no effect if SIP registration settings is set to No registration.

The login name for the MCU on the SIP registrar.

You need to configure the SIP registrar with details of the devices that will register with it and create a login for each device.

If you are using Microsoft OCS or LCS, you need to enter the full URI (for example, MCU@example.com).

Note that this username will be used anywhere where one is required in a SIP call; for example, it will be used where authentication is required with a SIP server where no registrar is used.

The password for the MCU on the SIP registrar.

You need to configure the SIP registrar with details of the devices that will register with it and create a login for each device. The password configured on this page needs to match the password in the SIP registrar.

Note that this username will be used anywhere where one is required in a SIP call; for example, it will be used where authentication is required with a SIP server where no registrar is used.

This field controls whether any conferences' configured numeric IDs are allowed to be registered with the registrar.

This setting is the global control that allows or disallows conferences to be registered with the SIP registrar.

Individual conferences will be registered or not depending on the per-conference Numeric ID registration setting which is on the Add conference page for scheduled conferences and for ad hoc conferences it is in the ad hoc conference template.

This would normally be Enabled; by setting it to Disabled, an administrator can prevent users from adding to the set of IDs registered with the configured registrar, even if those users enable the registrar Numeric ID registration setting for conferences they control. This may be desired when working with certain types of SIP registrars whose behavior in some modes is to disconnect active calls when the set of registered IDs changes.

This setting affects both the registration of numeric IDs configured for scheduled conferences and the registration of the numeric IDs of ad hoc conferences.

This field will have no effect if SIP registrar usage is set to Disabled.

Identifies the network address of the SIP proxy.

If set, the proxy is used for all SIP calls, whether through a registrar or not.

Select a maximum bit rate to use from Microsoft OCS/LCS clients.

Microsoft OCS/LCS clients will try to use the maximum bit rate that the MCU advertises during the initial call setup. In most scenarios, you will not want OCS/LCS clients to use the Default bandwidth from MCU that is configured on the Settings > Conferences page (Configuring global conference settings). Use this setting to select an appropriate bit rate for Microsoft OCS/LCS clients.

<limit disabled> will cause the MCU to advertise the Default bandwidth from MCU.

Identifies the protocol to be used for call control messages for outgoing call connections.

If your SIP devices use TCP, select TCP as the outgoing transport. If your SIP devices use UDP, select UDP as the outgoing transport. If you want to use encrypted SIP, select TLS. Note that if you want to use TLS, you must have the encryption feature key (or the Secure management feature key) and the TLS service must be enabled on the Network > Services page.

Note that this unit-wide setting can be overridden on a per-configured endpoint basis if you require different settings for individual endpoints. For more information about configuring SIP endpoints, refer to Configuring SIP endpoints

Using TLS for call setup is not sufficient for the call to be considered encrypted such that it can participate in a conference which requires encryption. Where encryption is required in the conference configuration, a SIP call must use SRTP. For more information about SIP encryption, refer to Configuring encryption settings.

The MCU can accept connections on TCP, UDP, and TLS providing those services are enabled on the Network > Services page (Configuring network services).

Select this option to force the MCU to present its local certificate when registering with the SIP registrar and when making outgoing TLS calls.

Often, the SIP registrar will not require the local certificate from the MCU. Only select this option if your environment dictates that the SIP registrar must receive the local certificate.

Select whether to enable streaming, ConferenceMe, or neither.

To enable streaming, select Streaming from the drop-down menu.

To enable ConferenceMe, select ConferenceMe from the drop-down menu.

If you would like to disable both streaming and ConferenceMe, select None.

The MCU is configured with two streaming rates, each comprising audio and video encoding formats (codecs) and overall (i.e. combined) media bit rate. The names you enter are the choices offered to users when streaming.

This is intended to make the choice easier for potentially non-technical users; for instance, one rate could be named "low bit rate" and the other "high bit rate".

The name is optional - if not specified, the choices offered to users will simply show the details of the audio and video codecs, together with the overall media bit rate.

Select from the available media players.

It is not possible to use Windows Media Player to stream conferences in multicast mode.

Sets the audio and video combination to use, and the overall media bit rate.

Typically, when two streaming rates are used, one is set up as a low bit rate combination and the other configured to use a higher bit rate. This enables those users with a low bandwidth connection to achieve useful streaming while at the same time allowing those with a high bandwidth link to take advantage of enhanced video.

The available options vary depending on which media player you have chosen.

Choose whether to use the specified streaming rate for multicast.

If this is set to Enabled then for any conference with Streaming set to Multicast or Unicast and multicast, multicast audio and video streams will be transmitted according to the corresponding streaming settings.

Setting any Multicast parameters to Enabled will only be useful if the multicast media IP addresses and port numbers are also configured - see below.

It is not possible to use Windows Media Player to stream conferences in multicast mode.

Identifies the range of IP addresses to which multicast streaming media should be sent.

If this address range is not configured, the MCU cannot transmit multicast conference media.

Sets the range of port numbers to which the media will be sent.

This UDP port number range is used in conjunction with the Media transmit IP address.

You must set both the start and end port numbers to transmit multicast conference media.

Identifies the protocol used by Windows Media Player to stream data. Note that v11 only supports HTTP; it no longer supports MMS over UDP or MMS over TCP.

MMS over UDP is a low latency/ high throughput protocol, while MMS over TCP includes extra reliability, though extra processing power is required. Both use the streaming port, so if a restrictive firewall is present HTTP may be necessary.

Auto negotiation attempts to open the most efficient connection, switching protocols if unable to do so, but on some systems this is not efficient. TANDBERG recommends that you select to use UDP/TCP/HTTP rather than auto-negotiation.

Controls the ability of the MCU to connect using TCP if a UDP connection is not available.

ConferenceMe can connect using either UDP or TCP. When connecting using UDP, ConferenceMe will have better network performance, resulting in better video being sent to and received from the MCU.

The maximum number of ConferenceMe participants allowed on the MCU.

Allows you to define the number of ConferenceMe connections on your MCU, from a minimum of 0 to a maximum of 12. That is, you can have the defined number of participants in one conference or shared across several conferences.

The maximum bandwidth that can be sent from your MCU to ConferenceMe.

The maximum bandwidth that can be received by your MCU from ConferenceMe.

Controls whether the MCU as a whole is 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 Adding and updating conferences.

If this setting is Disabled, no conference will be able to use content.

If this setting is H.239 only, no conference 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 TANDBERG Codian 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).

This field sets which video codec is used for conferences' content video streams.

A single content video stream is used for each conference, and this stream will be sent to all viewing endpoints. If an endpoint is unable to receive content video using the codec configured here, no content channel will be opened to that endpoint.

This field sets a lower limit on the bandwidth of the shared content video encoding sent to content receivers in a conference.

Changing this setting when there are connected participants causes the MCU to re-assess whether there should be content video channels to those endpoints; the MCU will close existing channels and open new ones as appropriate.

A single content video stream is used for each conference, and this stream will be sent to all endpoints receiving the content channel as a separate video channel. If some endpoints are only able to receive low bit rate streams (for instance if they have called into the MCU at a low call rate), it is sometimes preferable to exclude those endpoints completely from the content stream rather than force all viewers to see a reduced bit rate channel.

If you do not wish to exclude endpoints from viewing the shared content video channel in a conference, make sure this is set to <no minimum>, which is the default setting.

Where an endpoint cannot, for whatever reason, receive the content channel as an additional video channel, the MCU can show the content channel as part of the main video channel. That is, the participant will see the content as a pane in the conference layout. This functionality is controlled by the Display content in normal video channel setting (see below).

Note that during a call, an endpoint can send a 'flow control message' to the MCU that could cause the MCU to reduce the bit rate to that endpoint to below the configured Minimum content channel bit rate; in this case, the MCU will close the content channel to that participant. To re-enable content (which has been disabled in this way) to this participant, go to the conference's Participant list and use the content enable control. For more information about altering a participant's settings during a conference, refer to Viewing the conference participant list.

Sets whether the MCU will render content channel data in endpoints' main video channels.

If there is an active content channel for a conference, it may be that the MCU is unable to open a content channel to a particular endpoint. For instance, that endpoint may have no content capability, or might not support the video format specified by the Outgoing content video codec setting (see above).

In these cases, if this option is set to Enabled, the MCU will display the content channel video within a pane of the currently selected conference layout. In these cases, you might also want to enable the Automatically make content channel important option in the Settings > Conferences page which will make the content channel important at the same time.

Note that SIP endpoints receive content from the MCU in the normal video channel (rather than in a separate channel). For this reason, this option must be enabled to allow SIP participants to see content.

If this option is Enabled, the MCU will ignore fast update requests for a conference's content video channel received from endpoints whose connections are experiencing problems.

When this mode is active, it can prevent a large number of keyframes being sent in the shared content video encoding in response to fast update requests from a single endpoint. A high number of keyframes may reduce the video quality of the content channel for all conference participants, including those with good connections to the MCU.

Sets the bandwidth of the content channel video stream sent to streaming viewers.

This option is only available if the MCU web conferencing (WCO) feature key is present.

Just as there is a single content video stream sent to all content-capable video conferencing endpoints in a conference, there is a single content channel video stream sent to all streaming viewers.

This option allows the bandwidth of the streamed content channel video to be set. While in general a higher value means a greater frame rate (and thus better video quality), it is important to not set this value too high (i.e. higher than the available TCP network bandwidth between the MCU and viewers' machines) to avoid degradation resulting from lost data.

If Enabled, people viewing the content channel stream via a web browser will be able to add markup to that video stream such as graphics and text. This markup will then be visible to all content channel viewers, both those viewing via streaming and those connected via videoconferencing endpoints.

This option is only available if the MCU web conferencing (WCO) feature key is present.

Changing this setting has an immediate effect:

• if changed to Disabled, it will not be possible for existing viewers to complete markup currently in progress
• if changed to Enabled, existing streaming viewers will gain the ability to add markup

Allows for rapid swapping between content from different participants in a video conference. In a conference where a participant is sending content, this feature allows another endpoint to start sending content without having to wait for the current content provider to stop sending content from his computer.

The MCU applies this feature unit-wide. Therefore when it is enabled, all conferences on the MCU will allow automatic content handover.

This option is disabled by default.

Whether the MCU is able to use encryption or not.

When encryption status is Enabled, the MCU advertises itself as being able to use encryption and will use encryption if required to do so by an endpoint. If this setting is Enabled, you can enable or disable the use of encryption on a per-conference basis.

If this setting is Disabled, no conference will be able to use encryption.

Select the setting for media encryption for SIP calls:

• All transports: If encryption is used for a call, the media will be encrypted using SRTP regardless of transport mechanism used for call control messages.
• Secure transports (TLS) only: If encryption is used for a call, the media will only be encrypted in calls that are set up using TLS.
• Disabled: SRTP will not be used for any calls. The MCU will not encrypt media for SIP calls.

For more information refer to Using encryption with SIP, below.

When disabled, the MCU will not advertise that it is able to encrypt using SRTP. It is only necessary to disable SRTP if it is causing problems.

Advanced account security mode causes the MCU to hash passwords before storing them in the configuration.xml file (see below). Note that hashing user passwords is an irreversible process.

Before you enable advanced account security mode, we recommend that you back up your configuration. The MCU gives you the option to do that after you have enabled Advanced account security mode.

If you enable advanced account security mode, all current passwords (created when the MCU was not in advanced account security mode) will expire and users must change them.

Advanced account security mode is described in greater detail below.

Enable this option to have HTTP requests to the MCU automatically redirected to HTTPS.

This option is unavailable if either HTTP (Web) or HTTPS (Secure web) access is disabled on the Network > Services page.

The timeout setting for idle web sessions. The user must log in again if the web sessions expires. The timeout value must be between 1 and 60 minutes. Note that status web pages that auto-refresh will keep a web session active indefinitely. You can configure the MCU not to auto-refresh those pages; to do so, go to Settings > User interface .

The serial console interface displays log messages. If that is considered to be a security weakness in your environment, select this option to hide those messages.

Select this option for enhanced serial port security.

Select this option to require an administrator login by anyone attempting to connect to the MCU via the console port. If this is not enabled, anyone with physical access to the MCU (or with access to your terminal server) can potentially enter commands on the serial console.

If you have enabled Require administrator login , you can configure a session timeout period. The timeout setting for idle console sessions. The admin must log in again if the console sessions expires. The timeout value must be between 1 and 60 minutes.

Specifies whether the port should be configured manually or automatically. If set to Automatic via DHCP the MCU obtains its own IP address for this port automatically via DHCP (Dynamic Host Configuration Protocol). If set to Manual the MCU will use the values that you specify in the Manual configuration fields below.

Click Renew DHCP to request a new IP address if you have selected automatic configuration.

Port A should never be disabled because it is the primary interface of the MCU.

The dot-separated IPv4 address for this port, for example 192.168.4.45.

You only need to specify this option if you have chosen Manual IP configuration, as described above.

For Port A, if the IP configuration setting is set to Automatic by DHCP this setting will be ignored.

The subnet mask required for the IP address you wish to use, for example 255.255.255.0

The IP address of the default gateway on this subnet, for example 192.168.4.1

Specifies a name for the MCU.

Depending on your network configuration, you may be able to use this host name to communicate with the MCU, without needing to know its IP address.

The IP address of the name server.

Identifies an optional second name server.

The secondary DNS server is only used if the first is unavailable. If the first returns that it does not know an address, the secondary DNS server will not be queried.

Specifies an optional suffix to add when performing DNS lookups.

This can allow you to use non-fully qualified host names when referring to a device by host name instead of IP address.

For example, if the domain name is set to tandberg.com, then a request to the name server to look up the IP address of host endpoint will actually lookup endpoint.tandberg.com.

Specify whether you want this Ethernet port to automatically negotiate its Ethernet settings with the device it is connected to, or if it should use the values that you specify in the Manual configuration fields below.

It is important that your Ethernet settings match those of the device to which this port is connected. For example, both devices must be configured to use automatic negotiation, or both configured with fixed and matching speed and duplex settings (see below).

Identifies the connection speed: 10 Mbit/s or 100 Mbit/s. Use automatic negotiation if a connection speed of 1000 Mbit/s is required.

The connection speed must match that of the device to which this port is connected.

You only need to select this option if you have chosen Manual Ethernet settings, as described above.

Identifies the connection duplex mode:

• Full duplex
  Both devices can send data to each other at the same time
• Half duplex
  Only one device can send to the other at a time

The duplex setting must match that of the device to which this port is connected.

You only need to select this option if you have chosen Manual Ethernet settings, as described above.

Indicates whether this Ethernet port is connected to or disconnected from the network.

The speed (10/100/1000 Mbit/s) of the network connection to the MCU on this port.

This value is negotiated with the device to which this port is connected or based on your Manual configuration selected above.

The duplex mode (Full duplex or Half duplex) of the network connection to this port.

This value is negotiated with the device to which this port is connected or based on your Manual configuration selected above.

The fixed hardware MAC (Media Access Control) address of this port.

This value cannot be changed and is for information only.

Displays a count of the total number of packets sent from this port by the MCU. This includes all TCP and UDP traffic.

When troubleshooting connectivity issues, this information can help you confirm that the MCU is transmitting packets into the network.

Displays a count of the total number of packets received by this port of the MCU. This includes all TCP and UDP traffic.

When troubleshooting connectivity issues, this information can help you confirm that the MCU is receiving packets from the network.

These fields display further statistics for this port.

• Multicast packets sent
• Multicast packets received
• Total bytes sent
• Total bytes received
• Receive queue drops
• Collisions
• Transmit errors
• Receive errors

Use these fields for advanced network diagnostics, such as resolution of problems with Ethernet link speed and duplex negotiation.

The IP address to which the MCU will send packets in the absence of more specific routing (see IP routes configuration).

If Ethernet Port B is disabled, you cannot specify that port as the default gateway preference.

Selecting Port B as default gateway preference then disabling Port B will cause the preference to revert to Port A.

The IP address to which the MCU will send requests to look up unrecognized host names in order to determine their corresponding IP addresses. Only one name server (and associated secondary name server) may be used, even though different name servers may have been configured for Ports A and B. Use this option to decide which port's name server configuration to use as the unit's name server.

If Ethernet Port B is disabled, you cannot specify that port as the name server preference.

Selecting Port B as name server preference then disabling Port B will cause the preference to revert to Port A.

Use these fields to define the type of IP addresses to which this route applies.

The IP address pattern must be in the dot-separated IPv4 format, while the mask length is chosen in the IP address / mask length field.

The mask field specifies how many bits of the address are fixed; unfixed bits must be set to zero in the address specified.

To route all IP addresses in the range 192.168.4.128 to 192.168.4.255 for example, specify the IP address as 192.168.4.128 and the mask length as 25, to indicate that all but the last seven bits address are fixed.

Use this field to control how packets destined for addresses matching the specified pattern are routed.

You may select Port A, Port B or Gateway. If Gateway is selected, specify the IP address of the gateway to which you want packets to be directed.

If Ethernet Port B is disabled, the option to route packets to Port B will be disabled.

Enable/disable web access on the specified interface or change the port that is used for this service.

Web access is required to view and change the MCU web pages and read online help files. If you disable web access on both Ports A and B you will need to use the serial console interface to re-enable it.

Note that QuickTime uses RTSP by default which is listed as Streaming (other) on the Network > Services page. However, the QuickTime player can be configured to use HTTP (that is it will come from the web service port) instead.

If you require advanced security for the MCU, disable web access.

If a port is disabled, this option will be unavailable.

Enable/disable secure (HTTPS) web access on the specified interface or change the port that is used for this service.

This field is only visible if the MCU has the Secure management (HTTPS) feature key or an Encryption feature key installed. For more information about installing feature keys, refer to Upgrading and backing up the MCU.

By default, the MCU has its own SSL certificate and private key. However, you can upload a new private key and certificates if required. For more information about SSL certificates, refer to Configuring SSL certificates.

If a port is disabled, this option will be unavailable.

Enable/disable the ability to receive incoming calls to the MCU using H.323 or change the port that is used for this service.

Disabling this option will not prevent outgoing calls to H.323 devices being made by the MCU.

That is, the MCU will need to dial out to conference participants who are using H.323.

If a port is disabled, this option will be unavailable.

Allow/reject incoming calls to the MCU using SIP over TCP or change the port that is used for this service.

Disabling this option will not prevent outgoing calls to SIP devices being made by the MCU. That is, the MCU will need to dial out to conference participants who are using SIP over TCP.

If a port is disabled, this option will be unavailable.

Allow/reject incoming encrypted SIP calls to the MCU using SIP over TLS or change the port that is used for this service.

Disabling this option will not prevent outgoing calls to SIP devices being made by the MCU. That is, the MCU will need to dial out to conference participants who are using SIP over TLS.

If a port is disabled, this option will be unavailable.

Allow/reject content streams using BFCP (Binary Floor Control Protocol).

Disabling this option will prevent BFCP content being used in any conferences. BFCP can be used to allow SIP endpoints to contribute and receive content. For more information, refer to Content channel video support.

Allow/disable streaming from the MCU to Windows Media Player or change the port that is used for this service.

If a port is disabled, this option will be unavailable.

For more information about streaming, refer to Configuring streaming settings.

Allow/disable RTSP (Real Time Streaming Protocol) streaming from the MCU to QuickTime or RealPlayer or change the port that is used for this service.

If a port is disabled, this option will be unavailable.

For more information about streaming, refer to Configuring streaming settings.

Enable/disable FTP access on the specified interface or change the port that is used for this service.

FTP can be used to upload and download MCU configuration.

You should consider disabling FTP access on any port that is outside your organization's firewall.

If you require advanced security for the MCU, disable FTP access.

If a port is disabled, this option will be unavailable.

Enable/disable the receiving of the SNMP protocol on this port or change the port that is used for this service.

If a port is disabled, this option will be unavailable.

You must use the same port number for both Port A and Port B. The number is automatically refreshed for Port B. You cannot change the Port B UDP port numbers and they are always grayed-out; if you want to enable the receiving of the SNMP protocol on Port B, ensure that you have the video firewall as an activated feature (refer to Upgrading and backing up the MCU) and you have selected the check box for SNMP on Port B.

Note that by default SNMP Traps are sent to port UDP port 162 (on the destination network management station); this is configurable. For more information, refer to Configuring SNMP settings.

If you require advanced security for the MCU, disable the SNMP service.

Allow/reject incoming and outgoing calls to the MCU using SIP over UDP or change the port that is used for this service.

Disabling this option will prevent calls using SIP over UDP.

If a port is disabled, this option will be unavailable.

You must use the same port number for both Port A and Port B. The number is automatically refreshed for Port B. You cannot change the Port B UDP port numbers and they are always grayed-out; if you want to allow incoming and outgoing SIP (UDP) calls on Port B, ensure that you have the video firewall as an activated feature (refer to Upgrading and backing up the MCU) and you have selected the check box for SIP (UDP) on Port B.

Enable/disable access to the built-in H.323 gatekeeper or change the port that is used for the built-in H.323 gatekeeper.

If a port is disabled, this option will be unavailable.

You must use the same port number for both Port A and Port B. The number is automatically refreshed for Port B. You cannot change the Port B UDP port numbers and they are always grayed-out; if you want to open Port B for the H.323 gatekeeper, ensure that you have the video firewall as an activated feature (refer to Upgrading and backing up the MCU) and you have selected the check box for H.323 gatekeeper on Port B.

Enable/disable tunneled media calls to the MCU over UDP

This option must be enabled to allow TANDBERG ConferenceMe to connect over UDP. This option is only available if you have the Web Conferencing feature key installed.

Identifies the MCU in the SNMP system MIB.

Usually you would give every device a unique name. The default setting is:
Codian MCU

The location that appears in the system MIB.

An optional field. It is useful where you have more than one MCU to identify where the unit is located. The default setting is:
Unknown

The contact details that appear in the system MIB.

An optional field. The default setting is:
Unknown

Add the administrator’s email address or name to identify who to contact when there is a problem with the device. If SNMP is enabled for a port on the public network, take care with the details you provide here.

A description that appears in the system MIB.

An optional field, by default this will indicate the model number of the unit. Can be used to provide more information on the MCU.

Select this check box to enable the MCU to send traps.

If you do not select this check box, no traps will be sent.

Select this check box to enable authentication failure traps.

You cannot select this check box unless you have selected to Enable traps above. Authentication failure traps are generated and sent to the trap receivers when someone tries to read or write a MIB value with an incorrect community string.

Enter the IP address or hostname for up to four devices that will receive both the general and the authentication failure traps.

The traps that are sent by the MCU are all SNMP v1 traps. You can configure trap receivers or you can view the MIB using a MIB browser. You can set the UDP port number for the trap in the format <IP address>: <port number>. By default the UDP port number is 162.

Community string/password that gives read-only access to all trap information.

Note that SNMP community strings are not secure. They are sent in plain text across the network.

It is advisable to change the community strings before enabling SNMP as the defaults are well known.

Community string/password that gives read/write access to all trap information.

Community string/password that is sent with all traps.

Some trap receivers can filter on trap community.

Six bit binary field for prioritizing audio data packets on the network.

Do not alter this setting unless you need to.

Six bit binary field for prioritizing video data packets on the network.

Do not alter this setting unless you need to.

If selected, use of the NTP protocol is Enabled on the MCU.

The offset of the time zone that you are in from Greenwich Mean Time.

You must update the offset manually when the clocks go backwards or forwards: the MCU does not adjust for daylight saving automatically.

The IP address or hostname of the server that is acting as the time keeper for the network.