TANDBERG Border Controller User Guide
Page 53 of 118
In order to achieve this:
1.
On the Gatekeeper, set
Calls to unknown IP addresses
to
Indirect.
This can be done via either:
xconfiguration Gatekeeper CallsToUnknownIPAddresses: Indirect
or
Gatekeeper Configuration
->
Gatekeeper
and in the
Configuration
section, from the
Calls to
unknown IP addresses
drop-down menu selecting
Indirect
.
This setting will mean that, when the Gatekeeper receives a call that was dialed using an IP
address, it will forward the calls to the TANDBERG Border Controller, thereby allowing the Border
Controller itself to relay the call to the endpoint on the public IP address. Note however that if
the IP address received by the Gatekeeper matches that of any subzone configured on the
Gatekeeper, it will attempt to place the call locally and will not forward it to the Border Controller.
2.
On the Border Controller, set
Calls to unknown IP addresses
to
Direct
.
This setting will allow the Border Controller to connect any call that it receives from the internal
Gatekeeper out to systems on the public Internet.
3.
From Endpoint 1001, dial 213.228.193.162.
12.4.
Neighbored Enterprises
If two enterprises have deployed Border Controllers for firewall traversal, the two Border Controllers may
be neighbored to allow calls to be placed from one enterprise to another. Neighboring will reduce call
setup time compared to URI dialing (see
URI Dialing
, section 10). The disadvantage of neighboring is
that the Border Controllers have to be configured with each other's addresses before the call can be
made.
Each Gatekeeper and its matching Border Controller are neighbored as described in section 12.1.
Border Controllers A and B are then neighbored together.
12.5.
URI Dialing
12.5.1.
Enabling outgoing URI calls
If you wish to enable users from within your enterprise to call a user in another enterprise using URI
dialing, then the following configuration is required
1.
Enter the address of your DNS server on the Border Controller. This can be done via either:
Server Address: dns_server_ip_address
or
System configuration
>
IP
and in the
DNS
section, entering the address in one of the
Address
fields
2.
Enable URI dialing on the Border Controller. This is because you want to use the Border any
H.323 URI received. This can be done via either:
xConfiguration Gatekeeper DNSResolution Mode: On
or
Border Controller Configuration
->
Gatekeeper
and in the
Configuration
field, ticking the
Allow
.
3.
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
xConfiguration Gatekeeper DNSResolution Mode: On
or
Gatekeeper Configuration
>
Gatekeeper
and in the
Configuration
field, ticking the
Allow DNS
Resolution
box.
4.
Configure the same local domain name on both the Gatekeeper and the Border Controller.
When an endpoint in your enterprise dials the full H.323 URI of an endpoint in another enterprise (for
@EnterpriseB.com
), the call will be routed to your Border Controller. This will discover that Border
Controller B is registered in DNS as responsible for Enterprise B, and will route the call to it. Border
Controller B will receive the incoming call and route it accordingly.
