CUCM: Intercluster Trunk Gatekeeper Controlled

We can configure a ICT GK controlled for distributed call processing models. The GK will perform the bandwidth and CAC management for the intercluster calls.

Is recommended to assign each cluster to it’s own zone.  In our case zones (CUCM6 and CUCM7) The main difference between how a gateway a CME or a CUCM interacts with the GK is the fact the CUCM will not register the E164 number dynamically ( the GK will not keep up with every single DN). Therefore the GK routing decisions should based upon tech-prefix and zone-prefix.

In our lab the CUCM6 will contain extension range 6XXX and CUCM7 will handle 7XXX. The tech-prefix used will 1#.

1- Under Device / Gatekeeper add the GK IP Address.

2- Under Device / Trunk -> Add a new Intercluster Trunk Gatekeeper controlled Trunk.

3- The device name specified on the Trunk will be “H323-id” the CUCM will use to get registered with the GK.

Configure a CSS to reach internal extensions.  Configure the amount of significat digits. Because we will have to prepend the tech-prefix to the called number, we will end up with 1#6005. To avoid changes to the current dial plan configure the number of significant digits to 4

Fill in the information for the rest of the information for the  GK. Make sure to use the proper tech-prefix and zone name.

5-  Create a route pattern to point into the GK trunk. Under the called number modifications we will need to prepend the tech-prefix (1#).

7- Now we can move to the GK configuration. Create two local zones and add the zone-prefix for both. We will not configure bandwidth restrictions yet.

gatekeeper
zone local CUCM6 cisco.com 192.168.109.204
zone local CUCM7 cisco.com
zone prefix CUCM6 6… gw-priority 10 CUCM6_1
zone prefix CUCM7 7… gw-priority 10 CUCM7_1
no shutdown

8- Both clusters should now be registered with the GK.

CUCM-Mobility#show gatekeeper endpoints
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr  Port  RASSignalAddr   Port  Zone Name         Type    Flags
————— —– ————— —– ———         —-    —–
192.168.209.4   33465 192.168.209.4   32787 CUCM7             VOIP-GW
H323-ID: CUCM7_1
Voice Capacity Max.=  Avail.=  Current.= 0
192.168.208.10  53287 192.168.208.10  51211 CUCM6             VOIP-GW
H323-ID: CUCM6_1
Voice Capacity Max.=  Avail.=  Current.= 0

9- You should now be able to call across the GK trunk. Below is the gatekeeper main 10 output.

GK/gk_process: QUEUE_EVENT (minor 0) wakeup
GK/gk_rassrv_arq: arqp=0x70B91640,crv=0x3, answerCall=0
GK/gk_rassrv_sep_arq: ARQ Didn’t use GK_AAA_PROC
GK/gk_dns_query: No Name servers
GK/rassrv_get_addrinfo: (1#7006) Matched tech-prefix 1#
GK/rassrv_get_addrinfo: (1#7006) Matched zone prefix 7 and remainder 006
GK/gk_rassrv_get_ingress_network: returning default ingress network = 1
GK/rassrv_arq_select_viazone: about to check the source side, src_zonep=0x677BB5C4
GK/rassrv_arq_select_viazone: matched zone is CUCM6, and z_invianamelen=0
GK/rassrv_arq_select_viazone: about to check the destination side, dst_zonep=0x70E29B88
GK/rassrv_arq_select_viazone: matched zone is CUCM7, and z_outvianamelen=0
GK/gk_rassrv_get_ingress_network: returning default ingress network = 1
GK/gk_zone_get_proxy_usage: local zone= CUCM7, remote zone= CUCM6, call direction= 0, eptype= 67586 be_entry= 0
GK/gk_zone_get_proxy_usage: returns proxied = 0
GK/gk_gw_select_px: Source and destination endpoints in different local zones
GK/gk_zone_get_proxy_usage: local zone= CUCM6, remote zone= CUCM7, call direction= 1, eptype= 67586 be_entry= 0
GK/gk_zone_get_proxy_usage: returns proxied = 0
GK/gk_process: QUEUE_EVENT (minor 0) wakeup
GK/gk_rassrv_arq: arqp=0x70B91640,crv=0x8003, answerCall=1
GK/gk_rassrv_dep_arq: ARQ Didn’t use GK_AAA_PROC

Below is the debug h225 asnd1 from the GK.

value RasMessage ::= admissionRequest :
{
requestSeqNum 5252
callType pointToPoint : NULL
endpointIdentifier {“70AE2BF800000003”}
destinationInfo
{
dialedDigits : “1#7006
}
srcInfo
{
dialedDigits : “6005
}
srcCallSignalAddress ipAddress :
{
ip ‘C0A8D00A‘H
port 53287
}
bandWidth 1280
callReferenceValue 4
conferenceID ‘009E4D781500F1B504004F01C0A8CEA5’H
activeMC FALSE
answerCall FALSE
canMapAlias TRUE
callIdentifier
{
guid ‘009E4D781500F1B504004F01C0A8CEA5’H
}
gatekeeperIdentifier {“CUCM6”}
willSupplyUUIEs FALSE
}

*Jan 31 22:06:42.166: H225 NONSTD OUTGOING PDU ::=
value ACFnonStandardInfo ::=
{
srcTerminalAlias
{
e164 : “6005
}
dstTerminalAlias
{
e164 : “1#7006
}
}

*Jan 31 22:06:42.166: RAS OUTGOING PDU ::=
value RasMessage ::= admissionConfirm :
{
requestSeqNum 5252
bandWidth 1280
callModel direct : NULL
destCallSignalAddress ipAddress :
{
ip ‘C0A8D104‘H
port 33465
}
irrFrequency 240
nonStandardData
{
nonStandardIdentifier h221NonStandard :
{
t35CountryCode 181
t35Extension 0
manufacturerCode 18
}
data ‘00010180933801028040A339’H
}
willRespondToIRR FALSE
uuiesRequested
{
setup FALSE
callProceeding FALSE
connect FALSE
alerting FALSE
information FALSE
releaseComplete FALSE
facility FALSE
progress FALSE
empty FALSE
}
}

*Jan 31 22:06:42.178: RAS INCOMING PDU ::=
value RasMessage ::= admissionRequest :
{
requestSeqNum 27
callType pointToPoint : NULL
endpointIdentifier {“70B1DB1800000004”}
destinationInfo
{
dialedDigits : “7006
}
srcInfo
{
dialedDigits : “6005
}
srcCallSignalAddress ipAddress :
{
ip ‘00000000’H
port 53287
}
bandWidth 1280
callReferenceValue 32772
conferenceID ‘009E4D781500F1B504004F01C0A8CEA5’H
activeMC FALSE
answerCall TRUE
canMapAlias TRUE
callIdentifier
{
guid ‘009E4D781500F1B504004F01C0A8CEA5’H
}
gatekeeperIdentifier {“CUCM7”}
willSupplyUUIEs FALSE
}

*Jan 31 22:06:42.182: RAS OUTGOING PDU ::=
value RasMessage ::= admissionConfirm :
{
requestSeqNum 27
bandWidth 1280
callModel direct : NULL
destCallSignalAddress ipAddress :
{
ip ‘C0A8D104‘H
port 33465
}
irrFrequency 240
willRespondToIRR FALSE
uuiesRequested
{
setup FALSE
callProceeding FALSE
connect FALSE
alerting FALSE
information FALSE
releaseComplete FALSE
facility FALSE
progress FALSE
empty FALSE
}

Advertisements

Posted on January 31, 2010, in CUCM. Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: