Configuring H.323 endpoints

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>. Note that square brackets are mandatory for IPv6 addresses.

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/blade-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/blade-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/blade-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/blade-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.

When this setting is enabled, the red recording indicator dot is visible to other conference participants.

If enabled, this participant is labelled as a recorder on the conference participants page.

Determines whether this participant is a chair or a guest when in automatic lecture mode.

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

This field allows the MCU to be configured so that content can be exchanged with third party MCUs in multi-level cascaded conferences over H.323. Choose from:

• As master: The MCU only acts as master in H.239 token negotiation.
• As slave: The MCU acts as the slave in H.239 token negotiation and can send content to a master unit if it accepts the token request.
• As mimic slave: The MCU acts as a mimic slave in H.239 token negotiation and will try to send content to all other endpoints/units even if this unit (i.e. the MCU configured as a mimic slave) rejects the token request.

When exchanging content with an endpoint in a H.323 call, the MCU acts as a master unit and the endpoint as a slave unit for the purpose of H.239 token negotiation. However, in order for the MCU to exchange content with a cascaded third party MCU the MCU must appear to the third party MCU to be a slave unit. The MCU can be configured as a true slave, in which case content will only be sent if the third party MCU master accepts the token request, or as a mimic slave where content is sent to all other connected endpoints even if the third party MCU rejects the token request.

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/blade-wide codec selection on the Settings > Conference page.