TANDBERG MSE 8510 Manuel D’Utilisation
86
You can configure H.323 endpoints to work with the MCU by choosing
. This makes it easier
to add endpoints to conferences because you can choose names from a list rather than adding network addresses.
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.
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
contribute an IP VCR recording as his video stream (using the associated endpoint function, see
). 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
.
The name of the endpoint.
The IP address, host name, or an E.164 address
(phone number).
(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>.
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.
connects.
To configure a gateway on the MCU, go to
. For more information, refer to
These fields are used to identify incoming calls as
being from the endpoint:
being from the endpoint:
Name: This must be the name that the
endpoint sends to the MCU
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 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.
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.
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.
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.
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.
cannot change the display name.