Configuring Gateway Type
Next, the gatekeepers must be configured to route calls destined for outside the
company network (ISDN videoconference calls and local and long distance voice
calls).The technology prefix 8# will be used for ISDN calls via the ISDN
gateway in New York.Thus, Atlanta and Miami will route these calls to the
Boston gatekeeper (which manages the newyork zone).
The technology prefix 7# will be used for calls for which the gatekeeper has
no other routing defined. Since the prefixes defined in the previous section cover
voice calls within the company and the 8# technology prefix cover ISDN calls,
the 7# technology prefix will cover all voice calls destined for outside of the
company network.
For Atlanta:
gw-type-prefix 8# hopoff boston
gw-type-prefix 7#* default-technology
For Boston:
gw-type prefix 8# gw ipaddr 10.192.1.4
gw-type-prefix 7#* default-technology
For Miami:
gw-type-prefix 8# hopoff boston
gw-type-prefix 7#* default-technology
www.syngress.com
164 Chapter 5 • Voice and Video Gatekeeper Design
Note that the Boston gatekeeper must manually define the ISDN gateway’s
technology prefix and IP address because that gateway is not capable of registering
its technology prefix automatically.The Atlanta and Miami gatekeepers
define that 8# calls be sent to the Boston gatekeeper to force ISDN calls to the
ISDN gateway in the newyork zone (controlled by the Boston gatekeeper).
NOTE
Each CallManager should register with its gatekeeper using the
GateKeeperSupportedPrefix configuration. This will automatically register
technology prefixes with the gatekeeper, and alleviates the need to manually
define in the gatekeeper the technology prefixes supported by each
CallManager. In the example in this section, each CallManager will register
with the 7# technology prefix.