SVS; Reviewed:
WCH/MI 6/20/02
Solution & Interoperability Test Lab Application Notes
© 2002 Avaya Inc. All Rights Reserved.
2 of 20
Gatekeeper-ext.doc
1. Introduction
One of the functions of a Gatekeeper is to perform E.164 to IP address resolution based on a dial
plan. All remote calls within a Zone are sent to its Gatekeeper, where it is sent either to a
gateway or to another remote gatekeeper zone. These Application Notes describe how to
configure an Avaya™ IP600 Server to interoperate with Cisco’s Gatekeepers and Gateways.
2. Background
In the block diagram (Figure 1) below, the Avaya™ IP600 Server is represented as a Gatekeeper
and Gateway within one box. This is because in H.323 terms, the Avaya IP600 Server is a
Gatekeeper with an embedded or fixed Gateway. Avaya’s IP600 Gatekeeper provides address
translation and control access. Avaya’s embedded Gateway performs the media conversions.
Once an endpoint registers with the Gatekeepers (via RAS), call signaling messages between the
endpoint are routed through Avaya’s Gatekeeper. This method of call signaling is called
Gatekeeper Routed Call Signaling and is the method used by Avaya.
Avaya IP600
Gatekeeper
Gateway
Cisco 3660
Gatekeeper
Cisco4604
Gateway A
Cisco 1751
Gateway B
Zone 1
Zone 2
Figure 1: Block Diagram of IP600 Server and Cisco Gatekeeper
The configuration in Figure 2 is based on the block diagram depicted in Figure 1. In this
configuration, Avaya and Cisco are considered to be in peer gatekeeper zones; that is, the Avaya
Gatekeeper zone manages extensions 77XX, while Cisco Gatekeeper zone manages extensions
62XX and 66XX. When an extension in Zone 1 calls an endpoint in Zone 2, Zone 2 is
considered a remote zone to Zone 1. Likewise in the other direction, when an endpoint in Zone 2
calls an extension in Zone 1, Zone 1 is considered to be a remote zone to Zone 2.
