Filter
Top Products
TANDBERG Border Controller User Manual
Figure 17: Dialing a public IP address
In order to achieve this:
• Within the Gatekeeper configuration — set ”Calls to unknown IP addresses” to Indirect. This
setting will force the Gatekeeper to forward calls to any IP address it does not have locally
registered to the TANDBERG Border Controller, thereby allowing the Border Controller
itself to relay the call to the endpoint on the public IP address.
• On the Border Controller, configure ”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.
• From Endpoint 1001, dial 213.228.193.162
7.4 Neighbored enterprises
If two sites 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 U RI dialing (described in section 6). The disadvantage of
neighboring is that the Border Controllers have to be configured with each others addresses
before the call can be made.
Gatekeeper and matching Border Controller are neighbored as described in section 7.1. Border
Controller A and B are neighbored together, either with or without prefixes.
7.5 URI dialing from within the enterprise
This diagram shows a deployment to support URI dialing to other enterprises.
• Turn URI dialing OFF on the TANDBERG Gatekeeper. You want to use the Border Controller
to resolve any H.323 URI received.
• Ensure that DNS Resolution Mode is turned on at the TANDBERG B order Controller. You
want to use the Border Controller to resolve any H.323 URI received
• Configure the local domain name on both the Gatekeeper and the Border Controller.
• Configure the Border Controller with the address of a public DNS server.
27