Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

I am wondering .....Gatekeeper

i have a project: i have 30 cities,each city i use

3660 voice GW, each city can phone each other, so

should i use 2620 Gatekeeper h.323 for every city?

total 30 gatekeepers, or i just use one 2620 gatekeeper, total 1 gatekeeper ,

any ideas?

thank you

Cisco Employee

Re: I am wondering .....Gatekeeper

It makes more sense to me that you have 1 centralized gatekeeper, possibly with another centralized gatekeeper for redundancy, and have the 3660 gateways register to it.

New Member

Re: I am wondering .....Gatekeeper

thank you david

could you please tell me

which gatekeeper i should use: 3640 with IOS(W/H.323)

or call manager?

any good ideal?

thank you in advanced

Cisco Employee

Re: I am wondering .....Gatekeeper

CallManager does not include gatekeeper functionality.

As far as which IOS platform to use as a gatekeeper, you may need to look at how many calls per second processing you may need to do in worst case scenarios, and work with your account team to choose the right platform for the required performance.

New Member

Re: I am wondering .....Gatekeeper

Just to elaborate on the response as to why a single gatekeeper would be the correct way to go.

The gatekeeper just provides a consolidation of VoIP call routing configuration on one box that would otherwise have to reside on every one of your gateways.

The dial-peers on the originating side of a VoIP call are set up to consult the gatekeeper rather than having a fixed IP address set as the target for the call.

The idea would seem to be to reduce the amount of configuration on the gateways so that required changes can be effected on just one central box. I think that the system also responds better to a gateway going down since the gateway is supposed to send keepalives to the gatekeeper while it is up and available.

The fact that you still have to define all sorts of information ( like codec, fax rate, DTMF relay protocol ) in the dial-peers on the gateway, means that the gatekeeper solution is not as useful as it might be.

I haven't tried it, but I guess if you try to design a dial plan with your own custom prefixes you can keep the dial-peer on your gateways down.

By this I mean that you might prefix all E.164 numbers with '7' say, and just have a single dial-peer for destination-pattern '7T' on your gateways.

This assumes that you have no desire to use different dial-peer parameters between different destinations.

On your gatekeeper you can have separate entries for every E.164 prefix you want to handle in a distinct way ( 7-44 for UK, 7-1-561 if you happen to have a gateway in that area code ... ).

In a similar way you could use a 9 prefix for some kind of internal dial plan for interfacing into a network of company PBXs, and have just a single '9.......' voip dial-peer per gateway.

Like I say, this is all hypothetical, but it's the only way I can think of that makes a gatekeeper efficient in terms of a configuration maintenance reduction device.

New Member

Re: I am wondering .....Gatekeeper

Hi...How are your call Managers placed and configured, In case you have got multiple Call Managers and phones in multiple cities contacting the Call Managers, then you would have to configure your call Managers as Gateway, thus whenevr there is a Inter Call Manager call the Call Admission shall be performed by the Gatekeeper. Thus If you have got only one Gatekeeper then whenever there is an inter Call Manager call there shall be Call Admission Request over the WAN which shall load your WAN Links and Of course the COST...