TANDBERG CODIAN MCU 4500 Benutzerhandbuch
119
To configure gatekeeper settings, go to
.
You can configure the MCU to use a gatekeeper, which can make it easier for end-users to join conferences using
directory numbers rather than requiring them to know the IP address or host name of the MCU. The MCU can
register up to 100 IDs with the gatekeeper; these IDs comprise conferences' Numeric IDs, the MCU service prefix, and
the H.323 ID. If you need to register more than 100 IDs, use a prefix for MCU registrations to route calls to the MCU,
rather than registering individual conferences with the gatekeeper. The use of prefixes is described further in the table
below.
directory numbers rather than requiring them to know the IP address or host name of the MCU. The MCU can
register up to 100 IDs with the gatekeeper; these IDs comprise conferences' Numeric IDs, the MCU service prefix, and
the H.323 ID. If you need to register more than 100 IDs, use a prefix for MCU registrations to route calls to the MCU,
rather than registering individual conferences with the gatekeeper. The use of prefixes is described further in the table
below.
In this section:
Gatekeeper settings
Gatekeeper status
Refer to this table for assistance configuring the gatekeeper settings. After making any configuration changes, click
.
Enables the MCU to use an H.323 gatekeeper for
registration of numeric identifiers for its
conferences and/or auto attendants.
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.
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.
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
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
page (see
) 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.
gatekeeper, enter its host name or IP address.
Controls how the MCU identifies itself when
registering with its configured gatekeeper.
registering with its configured gatekeeper.
Codian 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:
gateway option unless you are using a service
prefix (in this case, use Gateway). Only use a
different option if you are: