Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Displaying the built-in gatekeeper registration list
Cisco TelePresence MCU Version 4.2 Printable online help
Page 128 of 252
Displaying the built-in gatekeeper registration
list
list
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.
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.
this number.
NOTE: The MCU can register with its own built-in gatekeeper. The MCU then counts as one
registered device. See
registered device. See
Configuring the built-in gatekeeper
To start the gatekeeper:
1. Go to Network > Services and select H.323 gatekeeper to open a port for the gatekeeper. (On
the MCU, ports are not open by default for security reasons.)
2. Go to Gatekeeper, select Enabled in the Status field and click Apply changes. If you attempt to
enable the built-in gatekeeper without opening the port, an error message is displayed.
Configuring neighboring gatekeepers
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.
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:
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:
Field
Field description
Usage tips
Status
Enables or disables the built-in
gatekeeper.
gatekeeper.
To use the built-in gatekeeper, you must
enable it here.
enable it here.
Neighbor gatekeeper
1 and 2
1 and 2
Enter the IP address(es), or
hostname(s) (or <host>:<port
number> to specify a port other
than the default of 1719 on the
neighboring gatekeeper), of the
neighboring gatekeeper(s).
hostname(s) (or <host>:<port
number> to specify a port other
than the default of 1719 on the
neighboring gatekeeper), of the
neighboring gatekeeper(s).
These are the gatekeepers to which the
built-in gatekeeper will send an LRQ if it
has received an ARQ to resolve an ID
which it does not currently have registered.
The built-in gatekeeper will then use the
information received from the neighbor(s)
to reply to the original request. Note that
square brackets are mandatory for IPv6
addresses.
built-in gatekeeper will send an LRQ if it
has received an ARQ to resolve an ID
which it does not currently have registered.
The built-in gatekeeper will then use the
information received from the neighbor(s)
to reply to the original request. Note that
square brackets are mandatory for IPv6
addresses.
Accept LRQs
Configures the built-in gatekeeper
to reply to LRQs from other
gatekeepers.
to reply to LRQs from other
gatekeepers.
These requests can come from any
gatekeeper which has the MCU's built-in
gatekeeper configured as one of its
neighbors.
gatekeeper which has the MCU's built-in
gatekeeper configured as one of its
neighbors.