Neighbor Gatekeepers - TANDBERG Gatekeeper User Manual

TANDBERG Gatekeeper User Manual
Figure 3: Selecting IP Protocol
By default,if you attempt to register an alias which has already been registered with the system,
your registration will be rejected. This helps you to identify when two users have a conflicting alias.
In some deployments an endpoint may frequently receive a new IP address, causing unwanted
registration rejections. When it tries to register, it may be rejected because the Gatekeeper
still has a registration from its old IP address. The Gatekeeper may be configured to allow an
endpoint to overwrite the old IP address with the command:
xConfiguration Gatekeeper Registration ConflictMode: <Overwrite/Reject>
Consult the endpoint documentation for information on how to configure it with a Gatekeeper.
NOTE When URI dialing is used to discover an endpoint, the URI used is based on either the
H.323 ID or the E.164 alias that the endpoint registered with. The local domain is then added to
this. For more information on URI dialing see section 7

3.5 Neighbor Gatekeepers

As you start deploying more than one Gatekeeper or Border Controller, it is useful to neighbor
the systems together so that they can exchange information about registered endpoints. Each
Gatekeeper or Border Controller forms an H.323 zone and is responsible for the endpoints within
that zone.
The simplest approach is to assign each endpoint a unique alias and divide the endpoint
registrations between the Gatekeepers and Border Controllers. Each Gatekeeper or Border
Controller is then configured with the addresses of all other Gatekeepers and Border Controllers.
When a system receives a call for an endpoint which is not registered with, it will send out a
9