Tandberg Data N3 - Manual (Page 15)

9
Remote zones can be configured through the web interface of the TANDBERG Gatekeeper
by navigating to Gatekeeper Configuration > Gatekeeper. See Figure 1 for a screenshot of
the configuration.
Figure 1 Screenshot of the Adding a New Zone configuration
NOTE
When using a local zone prefix do not start the E.164 aliases with the same digits as the local
prefix. If you do this the Gatekeeper will strip the digits equal to the prefix from the alias
thinking it is a call from another zone.
NOTE
If you want to use URI dialing (see section 3.9 , URI Dialing) to neighbor Gatekeepers you
should not use prefixes on your zones.
NOTE
If prefixing zones are used, all prefixes used must be unique to both the other zones as well
as to any other alias or service prefixes registered to the gatekeeper.
NOTE
If prefix mode is set to
“
Strip
”
rather than
“
Include
”
the gatekeeper will not send the remote
zone prefix to the far end gatekeeper in the Location Requests.
3.4 Alternate Gatekeepers
Alternate Gatekeeper support is provided to increase the reliability of your deployment. If one
Gatekeeper becomes unavailable, perhaps due to a network or power outage, another will be
used as an Alternate. Alternate Gatekeepers share responsibility for their endpoint
community: an individual endpoint may be registered with any one of the Alternates. You
should configure Alternate Gatekeepers identically for all registration and call features such
as authentication, bandwidth control and policy. If you do not do this, endpoint behavior will
vary unpredictably depending on which Alternate it is currently registered with. Alternate
Gatekeepers should also be deployed on the same LAN as each other so that they may be
configured with the same routing information such as local domain names and local domain
subnet masks.
Each Gatekeeper may be configured with the IP addresses of up to five Alternates. When an
endpoint registers with the Gatekeeper, it is presented with the IP addresses of all the
Alternates. If the endpoint loses contact with its initial Gatekeeper, it will seek to register with
one of the Alternates. This may result in your endpoint community
’
s registrations being
spread over all the Alternates.