Directory Gatekeepers


Directory Gatekeepers

In a ample network, configuring the prefixes of anniversary area on all of the gatekeepers can be

time consuming. A agenda attendant can be acclimated to abate the agreement accomplish on

nondirectory gatekeepers in a network. LRQ forwarding allows a attendant to be

appointed as a agenda attendant or cool gatekeeper. With this feature, it is alone necessary

to configure anniversary attendant with its own bounded zones and area prefixes, and a single

match-all wildcard prefix for the area of the agenda gatekeeper. Alone the directory

gatekeeper has to be configured with the abounding set of all zones and area prefixes aural the

network.

A agenda attendant is basically a attendant that assiduously LRQ letters to other

gatekeepers, in chase of E.164 resolution, as depicted in Figure 8-27. These LRQ messages

are triggered by added gatekeepers that charge to apperceive how to locate an E.164

address to action a call.

When abacus a agenda attendant to a network, accede these points:

■ Application agenda gatekeepers is a arrangement architecture decision.

■ Bounded zones and LRQ forwarding zones can be mixed.

■ An LRQ from a non-Cisco attendant cannot be forwarded.

Directory Attendant Characteristics

Gatekeepers accumulate clue of added H.323 zones and advanced calls appropriately. When

many H.323 zones are present, attendant agreement can become accelerated in administrative

terms. In ample VoIP installations, you can use a centralized agenda gatekeeper

that contains a anthology of all the altered zones and coordinates LRQ-forwarding

processes. In the case of agenda gatekeepers, you no best charge a full-mesh configuration

between interzone gatekeepers.

Figure 8-27 Agenda Gatekeepers

A agenda attendant is about a cool attendant that assiduously LRQ messages.

LRQ letters are RAS letters triggered by an ARQ bulletin from endpoints that are

forwarded from attendant to gatekeeper. There is a absolute of bristles hops for an LRQ message,

which allows up to a four-tier attendant hierarchy.

By application a agenda gatekeeper, you no best charge a abounding cobweb amid gatekeepers,

which is a above advantage. Agenda gatekeepers accumulate a punch plan and additionally serve as

a abeyant interface to added centralized applications. In a all-embracing Voice over IP (VoIP)

network, a centralized interface point is required. This interface can collaborate with other

applications and agreement suites, such as the Advanced Able Arrangement (AIN) in

Signaling System 7 (SS7), GKTMP avenue servers, and AAA.

Historically, agenda gatekeepers were acclimated alone in ample account provider wholesale

deployments. Nowadays, agenda gatekeepers are additionally acclimated in all-embracing enterprises.

For example, banks with a ample cardinal of Cisco Unified Communications Manager

Express sites can use a agenda attendant to interconnect the Cisco Unified

Communications Manager Express sites with anniversary other.

480 Authorized Self-Study Guide: Cisco Voice over IP (CVOICE)

Zone SanJose

Directory

Gatekeeper Area Chicago

Phone1-1

2001

Phone1-2

2002

Phone2-1

3001

Phone2-2

3002

GK1 GK2

Cisco Unified

Communications

Manager sends

an ARQ to

gatekeeper 1.

Dials 3002.

Sends an LRQ to

directory gatekeeper.

Forwards an LRQ

to attendant 2.

Responds with LCF

to attendant 1.

Gatekeeper 1 Attendant 2

DGK

Using hierarchical gatekeepers provides a cogent advantage in agreement of scaling. Figure

8-28 shows four arrangement deployments:

■ Small Network—Gateways Only: In the case of an H.323 arrangement after gatekeepers,

a absolutely meshed punch plan is appropriate for anniversary gateway. This necessitates a significant

amount of authoritative work. One band-aid is to use a attendant as shown

in diagram 2.

■ Small Network—Simplified with a Gatekeeper: Gatekeepers accredit a connection

with anniversary aperture in the network, appropriately accouterment a axial area for the punch plan

and no best acute a full-mesh configuration.

■ Medium Network—Multiple Gatekeepers: In a medium-sized arrangement with multiple

gatekeepers, a abounding cobweb is appropriate amid the gatekeepers to allotment punch plan

information. Back a cardinal of H.323 zones are present, attendant configuration

can become administratively intensive.

■ Medium to Ample Network—Multiple Gatekeepers and a Agenda Gatekeeper:

In ample VoIP installations, a centralized agenda attendant that contains a registry

of all zones and coordinates LRQ forwarding can be used. This eliminates the need

for a full-mesh configuration.

For example, a ample blast aggregation ability use several gateways and ability accept one

gatekeeper amenable for all the gateways in one city. Another akin of centralization

could use a centralized agenda gatekeeper, sometimes alleged a cool gatekeeper, to

link assorted cities. This centralized attendant could be an interface to able route

engines for activating avenue management, for instance.

Redundancy is consistently an important affair to consider, but it is added important back you

are application a axial accessory like a agenda gatekeeper. If the agenda attendant shown

in diagram 4 fails, the added gatekeepers no best accept admission to the punch plan. The best

solution is for abounding back-up on all levels, including gateways, links, gatekeepers, directory

gatekeepers, and all added correlating services.

Chapter 8: Configuring H.323 Gatekeepers 481

Figure 8-28 Hierarchical Gatekeepers

Figure 8-29 shows basal aperture and attendant signaling amid zones, but this time

with a agenda gatekeeper.

482 Authorized Self-Study Guide: Cisco Voice over IP (CVOICE)

1. Small Network–Gateways Alone 2. Small Network–Simplified with a Gatekeeper

3. Medium Network–Multiple Gatekeepers

4. Medium to Ample Network–Multiple

Gatekeepers and a Agenda Gatekeeper

Gateway Gatekeeper

Directory

Gatekeeper

Figure 8-29 Agenda Attendant Signaling

Phone A places a alarm to buzz cardinal 408 555-2001 for Buzz B. Then the following

signaling action occurs:

1. Aperture A sends an ARQ to Attendant 1, allurement permission to alarm Buzz B.

2. GK1 does a lookup and does not acquisition Buzz B registered. GK1 does a prefix lookup

and finds a wildcard bout with the agenda gatekeeper. GK1 sends an LRQ to the

DGK.

3. GK1 sends a RIP bulletin to Aperture A.

4. The agenda attendant does a prefix lookup and finds GK2. It assiduously the LRQ

to GK2.

5. GK2 does a lookup and finds Buzz B registered. It allotment an LCF with the IP

address of Aperture B to the agenda gatekeeper.

6. The agenda attendant allotment an LCF to GK1.

7. GK1 allotment an ACF with the IP abode of Aperture B.

8. Aperture A sends a H.225 alarm bureaucracy bulletin to Aperture B with the buzz number

of Buzz B.

9. Aperture B sends an ARQ to GK2, allurement permission to acknowledgment the alarm from

Gateway A.

10. GK2 allotment an ACF with the IP abode of Aperture A to Aperture B.

11. Aperture B sends an active and a affix bulletin to Aperture A.

Chapter 8: Configuring H.323 Gatekeepers 483

Gateway A

Gatekeeper 1 Attendant 2

Directory

Gatekeeper

Phone A

GK1 DGK GK2

Gateway B

Phone B

408...

8

3 7

6

2

5

4

14

11

13

10

12

801...

1 9

12. Aperture B and Aperture A admit an H.245 adequacy barter and accessible logical

channels.

13. Aperture B sets up a POTS alarm to Buzz B at 408-555-2001.

14. Dual RTP streams are accustomed amid Aperture A and Aperture B.

Configuring Agenda Gatekeepers

Configuration of a agenda attendant is adequately straightforward. Figure 8-30 and

Examples 8-4, 8-5, 8-6, and 8-7 detail a archetypal agenda attendant configuration.

484 Authorized Self-Study Guide: Cisco Voice over IP (CVOICE)

DGK

SJCGK AUSGK NYCGK

SJCGW AUSGW

PSTN

408

PSTN

972

PSTN

212

NYCGW

V V V

10.1.1.1 10.2.1.1

10.4.1.1

10.3.1.1

Figure 8-30 Configuring Agenda Gatekeepers

Example 8-4 illustrates the agreement of the agenda gatekeeper.

Example 8-4 DGK Configuration

DGK#show running-config

... OUTPUT OMITTED ...

gatekeeper

zone bounded DGK cisco.com 10.4.1.1

zone alien SJCGK cisco.com 10.1.1.1 1719

zone alien AUSGK cisco.com 10.2.1.1 1719

zone alien NYCGK cisco.com 10.3.1.1 1719

zone prefix SJCGK 408*

zone prefix DFWGK 972*

Example 8-5 provides the agreement for the San Jose gatekeeper.

Example 8-5 SJCGK Configuration

Chapter 8: Configuring H.323 Gatekeepers 485

zone prefix NYCGK 212*

lrq forward-queries

lrq lrj immediate-advance

... OUTPUT OMITTED ...

SJCGK#show running-config

... OUTPUT OMITTED ...

gatekeeper

zone bounded SJCGK cisco.com 10.1.1.1

zone alien DGK cisco.com 10.4.1.1 1719

zone prefix SJCGK 408* gw-priority 10 SJCGW

zone prefix DGK *

... OUTPUT OMITTED ...

Example 8-6 shows the agreement for the Austin gatekeeper.

Example 8-6 AUSGK Configuration

AUSGK#show running-config

... OUTPUT OMITTED ...

gatekeeper

zone bounded AUSGK cisco.com 10.2.1.1

zone alien DGK cisco.com 10.4.1.1 1719

zone prefix AUSGK 972* gw-priority 10 AUSGW

zone prefix DGK *

... OUTPUT OMITTED ...

Example 8-7 demonstrates the agreement for the New York gatekeeper.

Example 8-7 NYCGK Configuration

NYCGK#show running-config

... OUTPUT OMITTED ...

gatekeeper

zone bounded NYCGK cisco.com 10.3.1.1

zone alien DGK cisco.com 10.4.1.1 1719

zone prefix NYCGK 212* gw-priority 10 NYGW

zone prefix DGK *

... OUTPUT OMITTED ...

Directory Attendant Configuration

You can complete the afterward tasks to configure a agenda gatekeeper:

Step 1. Create a distinct bounded area on the agenda attendant with a bounded address.

Step 2. Create alien zones for anniversary attendant controlled by this agenda gatekeeper

with addresses of alien gatekeepers.

Step 3. Specify area prefixes for the alien gatekeepers.

Step 4. Accredit forwarding of area requests.

Individual Attendant Configuration

You can complete the afterward tasks to configure an alone gatekeeper:

Step 1. Create a distinct bounded area on the attendant with a bounded address.

Step 2. Create a alien area for the agenda attendant with the abode of the

directory gatekeeper.

Step 3. Specify a area prefix to annals with the agenda gatekeeper.

Step 4. Specify the area prefix of the agenda gatekeeper.