| Index |
You can configure H.323 endpoints to work with the MCU by choosing Endpoints > Add H.323. This makes it easier to add endpoints to conferences because you can choose names from a list rather than adding network addresses. The MCU can also call a configured endpoint to add it to a conference.
A Codian IP VCR can be configured as an H.323 endpoint and added as a participant in a conference. If the IP VCR is configured to do so, it will start recording as soon as the conference starts. You can also configure a folder's Recording ID as an endpoint and in this way, when a conference starts, the IP VCR can start recording directly into a specific folder. For more information about using the IP VCR in this way, refer to the IP VCR's online help.
Recordings on a Codian IP VCR can be configured as H.323 endpoints. In this way, an audio-only participant can contribute an IP VCR recording as his video stream (using the associated endpoint function, see Adding and updating users). This function is also useful where you have a recording that you might like to view within a conference.
Refer to the table below for tips on adding an H.323 endpoint to the MCU. After entering the settings, click Add endpoint.
| Field | Field description | Usage tips |
|---|---|---|
| Name | The name of the endpoint. |
|
| Address | 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>. |
| H.323 gateway | The gateway through which the endpoint connects. |
|
| H.239 video contribution | Whether this endpoint is permitted to contribute the conference content channel using H.239. |
This setting takes precedence over the per-conference H.239 contribution setting for conferences that the endpoint is invited into. |
| H.239 video receive | Whether this endpoint is allowed to receive a separate H.239 video stream when in a conference. |
|
| Call-in match parameters | These fields are used to identify incoming calls as being from 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. |
| Display name override | 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. |
| Motion / sharpness trade off | Choose whether to use the unit-wide setting for motion/sharpness trade off, or configure an individual setting for use with this endpoint. Choose from:
|
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. |
| Transmitted video resolutions | 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. |
| View border size | Choose a border size for this endpoint's transmitted video. |
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. |
| Default view family | 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. |
| Preferred bandwidth from MCU | 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). |
| Preferred bandwidth to MCU | 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). |
| Layout control via FECC / DTMF | Whether this endpoint is able to change their view layout via Far-End Camera Controls or DTMF tones. |
This setting takes precedence over the per-conference layout control setting for conferences that the endpoint is invited into. |
| Initial audio status | 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. |
| Initial video status | 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. |
| Automatic disconnection | 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 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. |
| Custom codec selection | 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. |
| (c) Copyright Codian 2003-2008, License information |