Cisco UC – Gatekeeper

By | 05/11/2014

See Cisco Unified Communications for architecture information

 

@Gatekeeper

1) Perform configuration in the central gatekeeper.

configure terminal
gatekeeper
 zone local CUCM1 domain.com [GK IP]
 zone local CUCM2 domain.com
 zone local GW1 domain.com
 zone local GW2 domain.com
 zone prefix CUCM1 [ROUTEPATTERN-CUCM1] gw-priority 10 [TRUNK_NAME]_1 //publisher
 zone prefix CUCM1 [ROUTEPATTERN-CUCM1] gw-priority 9 [TRUNK_NAME]_2 //subscriber
 zone prefix CUCM2 [ROUTEPATTERN-CUCM2] gw-priority 10 [TRUNK_NAME]_1 //publisher
 zone prefix CUCM2 [ROUTEPATTERN-CUCM2] gw-priority 9 [TRUNK_NAME]_2 //subscriber
 zone prefix GW1 [ROUTEPATTERN-GW1]
 zone prefix GW2 [ROUTEPATTERN-GW2]
 gw-type-prefix 1#* default-technology
 no shutdown
 bandwidth interzone default 130

Troubleshoot commands

show gatekeeper endpoints
show gatekeeper calls
show gatekeeper zone status
debug ras

@C UCM

2) Define the gatekeeper in the Device > Gatekeeper  setting up the name and the IP

3) Configure a Device > Trunk with the parameters H225 Trunk (Gatekeeper), name (it should be the same used above TRUNK_NAME], gatekeeper name [IP], terminal type gateway, technology prefix # and zone CUCM1 defined aboce

4) Configure a route pattern to forward the calls to the other systems through the Gatekeeper

@GW

5) Configure the h323 parameters

terminal monitor //will tell us when the gateway is registered into the gatekeeper
int loopback0
 h323-gateway voip interface
 h323-gateway voip bind srcaddr [LOOPBACK IP]
 h323-gateway voip h323-id GW1
 h323-gateway voip id [ZONE ABOVE GW1] ipaddr [GATEKEEPER IP] 
 h323-gateway voip tech-prefix 1#

gateway

6) Configure the dial-peers to forward calls to the gatekeeper. The default behavior of Gateways is to automatically register the DNs to the Gatekeeper. The command “no register e164” under the dial-peer avoids it.