Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Displaying the built-in gatekeeper registration 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.
H.323 IDs (e.g. Fredsendpoint) or prefixes.
Up to 25 devices can be registered without a feature key.
Note: The MCU can register with its own built-in gatekeeper. The MCU then counts as one registered
device. See
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.
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:
can:
n
send LRQs regarding unknown IDs to its neighbor(s)
n
reply to LRQs from other gatekeepers
n
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.
To use the built-in gatekeeper, you must
enable it here.
enable it here.
Neighbor
gatekeeper
1 and 2
gatekeeper
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).
<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.
Cisco TelePresence MCU Series 4.5 Online Printable Help
Page 141 of 278
Managing the built-in gatekeeper
Displaying the built-in gatekeeper registration list