Hi guys,
I have a small problem with the GK task in this lab !
Task summary:
1 zone (HQ) where 3 endpoints registers => 2x CUCM (Pub and Sub
obviously) + Br2
2 type prefix :
1# => Type prefix registered by CUCM
3# => Type prefix registered by BR2-RTR
Zone bandwidth small task.
I disagree with the Detailed Solution Guide that says:
HQ-RTR
Gatekeeper:
zone local HQ ipexpert.com
zone prefix HQ 1... gw-priority 10 gk-trunk_2
zone prefix HQ 1... gw-priority 9 gk-trunk_1
zone prefix HQ 5... gw-priority 10 gk-trunk_2
zone prefix HQ 5... gw-priority 9 gk-trunk_1
bandwidth total default 128
no shut
BR2-RTR
Int loo0
h323-gateway voip interface
h323-gateway voip id HQ ipaddr 10.10.110.1 1719
h323-gateway voip h323-id BR2-RTR
h323-gateway voip tech-prefix
gateway
===================================================
I kinda disagree with that since BR2 can also be used for 5... or 1...
because zone prefix HQ 1... will defines the prio for CUCM only but Br2
will still use priority 5 so it sill appears in the show gatekeeper gw-type.
For me you would have to disable Br2 for these prefix :
zone prefix HQ 1... gw-priority 0 BR2-RTR
zone prefix HQ 5... gw-priority 0 BR2-RTR
That was my first point regarding the task..
I have another problem with the next task which involve call routing
through the gatekeeper.
The task says that UCM phones can call UCME and vice and versa by
dialing the appropriate extensions (4 digits)
The solution guide says to create a simple RG/RL and RP ... Nothing
special in the RP nor RL
on BR2_RTR
dial-peer voice 3000 voip
dtmf-relay h245-alpha
incoming called-number 3...$
dial-peer voice 15 voip
destination-pattern [15]...$
session target ras
incoming called .
tech-prefix 1#
no vad
For me the call would fail because if you debug gatek main 10 you will
see that the GK will not match a tech prefix (step 1) but will match a
zone prefix for HQ (step 2). It will not match a default tech-prefix so
the call will fail.
For me you need to prefix in the RL with 3#,so the DNIS will be 3#3001
Then the type prefix 3# (step 1) will be matched.
The Zone prefix 3001 will be match too (step2)
Call will be routed to BR2-RTR that have the best priority for this zone
prefix
ARQ will be sent by gk-trunk_2
ACF will be sent by the GK to gk-trunk_2
Then call will be received by CME RTR_2
it will NEVER match dial-peer 3000 since the DNIS is 3#3000
the call will match dial-peer voice 15 since the ANI is 1001 and ANI is
used for inbound DP with the destination-pattern command)
So for me you have to do the following
voice translation-rule 15000
rule 1 /^3#/ //
voice translation-profile INBOUND_GK_DNIS
translated called 15000
dial-peer voice 3000 voip
incoming call 3#3...
translation-profile inc INBOUND_GK_DNIS
dtmf-relay h245-alpha
The call will here succeed and will use g729 (default in dial-peer
configuration)
In the other direction, the call will succeed since it will be prefixed
by CME with 1# (command in the DP)
Call will be accepted by GK for the same reason as above.
CUCM will then use the 4 significants digits in the trunk configuration.
What do you guys think ? :)
Thanks for letting me know :)
Nic
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
Are you a CCNP or CCIE and looking for a job? Check out
www.PlatinumPlacement.com
