Filter
Top Products
TANDBERG Border Controller User Manual
3.1.2 Root Account
The Border Controller provides a root account with the same password as the admin account.
This account should n ot be used in normal operation, and in particular system configuration
should not be conducted using this account: use the admin account instead.
3.2 Registration
Before an endpoint can use the Border Controller it must first register with it. There are two ways
an endpoint can register:
• Automatically.
• Manually by specifying the IP address of the Border Controller.
You can disable automatic registration on the Border Controller. See auto discovery in section
11.2 for more information.
When registering, the endpoint registers with one or more of the following:
• One or more H.323 IDs.
• One or more E.164 aliases.
Users of other registered endpoints can then call the endpoint by using either the H.323 ID, a
URI, an E.164 alias, or one of the services.
You should choose H.323 aliases which do not reveal sensitive information. Like e-mail addresses,
they are passed unencrypted when a call is made.
Consult the endpoint documentation for information on how to configure it with a Gatekeeper.
NOTE Only traversal enabled endpoints can register with a TANDBERG Border Controller. All
other registration requests will be rejected. Traversal enabled endpoints include all TANDBERG
Expressway endpoints and third party endpoints which support the ITU H.460.18 and H.460.19
standards.
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. See section 6
3.3 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 al ias 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
8