TANDBERG Gatekeeper - Manual (Page 47)

TANDBERG Gatekeeper User Guide
Page 47 of 105
11. Example Traversal Deployments
11.1. Simple Enterprise Deployment
Figure 20: Simple enterprise deployment
Figure 20 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 that provides firewall
traversal.
Endpoints 1001, 1002 should register with the Gatekeeper. Endpoint 1003 will register with the Border
Controller. The Gatekeeper and Border Controller are configured to work together to provide firewall
traversal.
11.1.1. Enabling outgoing URI calls
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. This can be done via either:
xConfiguration IP DNS Server Address: dns_server_ip_address
or System configuration > IP and in the DNS section, entering the address in one of the Address fields.
 Enable URI dialing on the Border Controller. This can be done via either:
xConfiguration Gatekeeper DNSResolution Mode: On
or Border Controller Configuration -> Gatekeeper and in the Configuration field, ticking the Allow DNS
Resolution box.
 Disable URI dialing 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 firewall. This can be done via the
same commands/paths as above.