Cisco Cisco TelePresence MCU 4510 Maintenance Manual
Accept
LRQs
LRQs
Configures the built-in gatekeeper to reply to LRQs
from other gatekeepers.
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.
Forward
LRQs for
unknown
IDs
LRQs for
unknown
IDs
Configures the built-in gatekeeper to send (or not to
send) LRQs regarding unknown IDs to its neighbor
(s). Choose from the options:
send) LRQs regarding unknown IDs to its neighbor
(s). Choose from the options:
n
Disabled: The MCU will only respond to LRQs
about IDs registered with itself. It will not forward
LRQs about IDs that are not registered with itself to
neighboring gatekeepers.
about IDs registered with itself. It will not forward
LRQs about IDs that are not registered with itself to
neighboring gatekeepers.
n
Enabled, using local return address: The MCU will
put, in the LRQ, its own address as the return
address for the LCF.
put, in the LRQ, its own address as the return
address for the LCF.
n
Enabled, using received return address: The MCU
will put, in the LRQ, the address of the gatekeeper
that originated the request as the return address
for the LCF. Use this option only if you are
configuring the MCU to operate in an environment
with a multiple-level gatekeeper hierarchy. For
example, the 'received address' is required by the
national gatekeepers connected to the Global
Dialing Scheme (GDS).
will put, in the LRQ, the address of the gatekeeper
that originated the request as the return address
for the LCF. Use this option only if you are
configuring the MCU to operate in an environment
with a multiple-level gatekeeper hierarchy. For
example, the 'received address' is required by the
national gatekeepers connected to the Global
Dialing Scheme (GDS).
Unless you have selected to Accept
LRQs, you cannot configure the MCU to
forward any LRQs.
LRQs, you cannot configure the MCU to
forward any LRQs.
Enabling using received return address
can be a significant security risk. Only use
this setting with proper cause.
can be a significant security risk. Only use
this setting with proper cause.
Accept
LCFs from
non-
neighbors
LCFs from
non-
neighbors
This setting enables the built-in gatekeeper to accept
LCF message responses from any IP address.
LCF message responses from any IP address.
This setting is for use in environments with
a multiple-level gatekeeper hierarchy. For
example, this feature is required by the
national gatekeepers connected to the
Global Dialing Scheme (GDS).
a multiple-level gatekeeper hierarchy. For
example, this feature is required by the
national gatekeepers connected to the
Global Dialing Scheme (GDS).
Enabling this setting can be a significant
security risk. Only use this setting with
proper cause.
security risk. Only use this setting with
proper cause.
Gatekeeper status
The number of registered devices is shown in the format X / Y where Y is the number of registered devices
that your built-in gatekeeper is licensed for. Equally, the total number of registered IDs is shown as Z / 1000,
where 1000 is the maximum number of registrations allowed over all registered devices.
that your built-in gatekeeper is licensed for. Equally, the total number of registered IDs is shown as Z / 1000,
where 1000 is the maximum number of registrations allowed over all registered devices.
Below these summary figures is a table showing individual registrations. Registrations can be viewed by
registered ID (the "ID view") or by device (the "Registration view"), giving complete and easily searchable
lists. Switch between the views by clicking on the appropriate button.
registered ID (the "ID view") or by device (the "Registration view"), giving complete and easily searchable
lists. Switch between the views by clicking on the appropriate button.
The Registration view shows the summary per device (also known as the registrant), while the ID view
shows individual registrations. This means that registrations from the same device are not necessarily listed
together in the ID view but the view can be sorted by Registrant or Index to help you identify IDs belonging to
the same registrant.
shows individual registrations. This means that registrations from the same device are not necessarily listed
together in the ID view but the view can be sorted by Registrant or Index to help you identify IDs belonging to
the same registrant.
ID view
Field
Field description
Usage tips
Cisco TelePresence MCU Series 4.5 Online Printable Help
Page 142 of 278
Managing the built-in gatekeeper
Displaying the built-in gatekeeper registration list