TANDBERG MCU 4500, MSE 8510 manual To start the gatekeeper, go to

The MCU contains a built-in gatekeeper with which devices can register multiple IDs. IDs can be numbers, H.323 IDs (e.g. Fredsendpoint) or prefixes.

Up to 25 devices can be registered without a feature key. Feature keys can be purchased to increase this number.

:The MCU can register with its own built-in gatekeeper. The MCU then counts as one registered device. See Configuring gatekeeper settings.

To start the gatekeeper, go to	and select the H.323 gatekeeper check box to open a port for the
gatekeeper. (On the MCU, ports are not open by default for security reasons.) Then go to		, select Enabled
in the Status field and click	. If you attempt to enable the built-in gatekeeper without opening the port,
an error message is displayed.

You can optionally configure the built-in gatekeeper with up to two neighboring gatekeepers. This means that if the built-in gatekeeper receives a request (known as an Admission Request or ARQ) to resolve an ID to an IP address and that ID is not currently registered with it then it will forward that request to its neighbor gatekeeper(s), as a Location Request (LRQ). The built-in gatekeeper will then use the information received from the neighbor(s) to reply to the original request.

You can also configure the behavior of the built-in gatekeeper on receipt of LRQs from another gatekeeper. It can:

send LRQs regarding unknown IDs to its neighbor(s) reply to LRQs from other gatekeepers

accept LCFs (Locations Confirms) from non-neighboring gatekeepers

Refer to this table for assistance when configuring the built-in gatekeeper:

Enables or disables the built-in gatekeeper.

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

Enter the IP address(es), or	These are the gatekeepers to which the built-in
hostname(s) (or <host>:<port	gatekeeper will send an LRQ if it has received an
number> to specify a port other than	ARQ to resolve an ID which it does not currently
the default of 1719 on the neighboring	have registered. The built-in gatekeeper will then
gatekeeper), of the neighboring	use the information received from the neighbor(s)
gatekeeper(s).	to reply to the original request.
Configures the built-in gatekeeper to	These requests can come from any gatekeeper

reply to LRQs from other gatekeepers. which has the MCU's built-in gatekeeper configured as one of its neighbors.

97