Filter
Top Products
TANDBERG Border Controller User Manual
7 Example Traversal deployments
7.1 Simple Enterprise deployment
Figure 15: Simple enterprise deployment
Figure 15 shows a typical enterprise deployment. Endpoints 1001, 1002 and a Gatekeeper are
deployed on a private network, separated from the public network by a firewall and NAT. Endpoint
1003 is on a separate private network, perhaps a home worker on an DSL connection. A Border
Controller is deployed on the public network to allow traversal across the firewalls.
Endpoints 1001, 1002 may be any H.323 compliant endpoint. They will use the TANDBERG
Gatekeeper to provide firewall traversal. Endpoint 1003 must be a TANDBERG endpoint which
provides firewall traversal.
Endpoints 1001, 1002 should register with the Gatekeeper. Endpoint 1003 will register with the
Border Controller. The Gatekeeper will be configured to register with the Border Controller, and
the Border Controller set with a traversal client name that matches the TraversalZone Name of
the Gatekeeper.
If you wish to be able to call using URI dialing in this deployment then the following configuration
is required.
• Enter the address of your DNS server on the Border Controller:
xConfiguration DNS Server Address: dns
server ip address
• Enable URI dialing on the Border Controller
xConfiguration Gatekeeper DNSResolution Mode: On
• Ensure that URI dialing is disabled on the Gatekeeper. This is because you wish calls to
be routed from the private network to the Border Controller in order to traverse the fir ewall.
xConfiguration URI Dialing Mode: Off
In order to be able to receive calls placed to example.com using URI dialing, configure the
following:
25