What tech prefix did the CCM server register as?
You have to strip off the tech prefix on CCM.  Use a translation pattern or 
significant digits.

There's a difference between a GATEWAY registering with a tech prefix, and 
putting the tech prefix in the dial-peer which becomes part of the dialed 
string.  You have to do some H323 audio and video conferencing to really get a 
full understanding of tech prefixes.  But we can fill in the gaps here.  We are 
just using tricks to steer the calls around the gatekeeper routing mechanism 
with different tech prefixes.  The Cisco documentation is a little advanced in 
the fact they they think you know about h323 already. You have to find an h323 
concepts book or perhaps whatever study material they use for the Gatekeeper 
CCVP, etc exams.
________________________________
From: ABIOLA ADEFILA [adefilabi...@gmail.com]
Sent: Sunday, October 04, 2009 3:05 PM
To: Michael Ciarfello
Cc: OSL Group
Subject: Re: [OSL | CCIE_Voice] calls between hq and br2

hello,
i added the h323-gateway voip tech-prefix 1# command to the CME and was able to 
call from HQ to br2  but i can not call from BR2 TO hq

Below is my gateway config
gatekeeper
 zone local HQ ipexpert.com<http://ipexpert.com> 10.10.200.3
 zone prefix HQ 1... gw-priority 10 gk_trunk_2
 zone prefix HQ 1... gw-priority 9 gk_trunk_1
 zone prefix HQ 3... gw-priority 10 BR2-RTR
 zone prefix HQ 5... gw-priority 10 gk_trunk_2
 zone prefix HQ 5... gw-priority 9 gk_trunk_1
 gw-type-prefix 1#* default-technology
 bandwidth total zone HQ 128
 bandwidth session zone HQ 16
 no shutdown

On the CME
interface Loopback0
 ip address 10.10.110.3 255.255.255.255
 ip ospf network point-to-point
 h323-gateway voip interface
 h323-gateway voip id HQ ipaddr 10.10.200.3 1719
 h323-gateway voip h323-id BR2-RTR
 h323-gateway voip tech-prefix 1#
 h323-gateway voip bind srcaddr 10.10.110.3


dial-peer voice 400 voip
 incoming called-number 3...
 dtmf-relay h245-alphanumeric
!
dial-peer voice 900 voip
 destination-pattern [15]...
 session target ras
 incoming called-number .

Thanks



On Sat, Oct 3, 2009 at 9:33 PM, Michael Ciarfello 
<mciarfe...@iplogic.com<mailto:mciarfe...@iplogic.com>> wrote:
OK, let's take one direction at a time.  CCM to CCME.  (5002 to 3002)

It looks like from the GK output, your got your ARQ.  Let's debug voip ccapi on 
the CCME router and see what we get.
Does the phone ring on the other side?

Where are you getting that message?  A voice message from the annunciator?  And 
your're getting that message when CCME is calling CCM?

For your CCME to CCM call, do you have the proper significant digits configured 
on the gatewa or stripping off the tech prefix?  (1#5002) Matched tech-prefix 1#
________________________________
From: 
ccie_voice-boun...@onlinestudylist.com<mailto:ccie_voice-boun...@onlinestudylist.com>
 
[ccie_voice-boun...@onlinestudylist.com<mailto:ccie_voice-boun...@onlinestudylist.com>]
 On Behalf Of ABIOLA ADEFILA 
[adefilabi...@gmail.com<mailto:adefilabi...@gmail.com>]
Sent: Saturday, October 03, 2009 1:23 PM
To: OSL Group
Subject: [OSL | CCIE_Voice] calls between hq and br2

Hello,

i have configured gatekeeper and trunk to call between the hq (5002) and 
br2(3002)

calls from either side will give you the message '' the person you are trying 
to call is not available''
below is the debug
anyone with an idea?
rgd


Q-RTR#debug gateke
HQ-RTR#debug gatekeeper main 10
HQ-RTR#
HQ-RTR#
Oct  3 18:29:47.027: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: got a TIMER 
event

Oct  3 18:29:47.027: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_handle_timers

Oct  3 18:29:47.027: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_handle_timers: managed 
timer expired 0x467BDFF8

HQ-RTR#
Oct  3 18:29:52.787: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
HQ-RTR#
Oct  3 18:29:58.567: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
Oct  3 18:29:58.567: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_arq: 
arqp=0x48FFA648,crv=0x4, answerCall=0
Oct  3 18:29:58.567: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_sep_arq: ARQ 
Didn't use GK_AAA_PROC
Oct  3 18:29:58.567: //809CCBBF0400/809CCBBF0400/GK/gk_dns_query: No Name 
servers
Oct  3 18:29:58.567: //809CCBBF0400/809CCBBF0400/GK/rassrv_get_addrinfo: (3001) 
Tech-prefix match failed.
Oct  3 18:29:58.567: //809CCBBF0400/809CCBBF0400/GK/rassrv_get_addrinfo: (3001) 
Matched zone prefix 3 and remainder 001
Oct  3 18:29:58.567: 
//xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_get_ingress_network: returning default 
ingress network = 1
Oct  3 18:29:58.567: //809CCBBF0400/809CCBBF0400/GK/rassrv_arq_select_viazone: 
about to check the source side, src_zonep=0x49005C44
Oct  3 18:29:58.567: //809CCBBF0400/809CCBBF0400/GK/rassrv_arq_select_viazone: 
matched zone is HQ, and z_invianamelen=0
Oct  3 18:2
HQ-RTR#9:58.567: //809CCBBF0400/809CCBBF0400/GK/rassrv_arq_select_viazone: 
about to check the destination side, dst_zonep=0x49005C44
Oct  3 18:29:58.567: //809CCBBF0400/809CCBBF0400/GK/rassrv_arq_select_viazone: 
matched zone is HQ, and z_outvianamelen=0
Oct  3 18:29:58.567: //809CCBBF0400/809CCBBF0400/GK/rassrv_get_addrinfo: No 
tech prefix

Oct  3 18:29:58.567: //809CCBBF0400/809CCBBF0400/GK/rassrv_get_addrinfo: Alias 
not found

Oct  3 18:29:58.567: 
//xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_get_ingress_network: returning default 
ingress network = 1
Oct  3 18:29:58.567: //809CCBBF0400/809CCBBF0400/GK/rassrv_get_addrinfo: 
Technology GW selected

Oct  3 18:29:58.575: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
Oct  3 18:29:58.575: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_arq: 
arqp=0x4900B48C,crv=0x8004, answerCall=1
Oct  3 18:29:58.575: //809CCBBF0400/809CCBBF0400/GK/gk_rassrv_dep_arq: ARQ 
Didn't use GK_AAA_PROC
Oct  3 18:29:58.583: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
HQ-RTR#
HQ-RTR#
Oct  3 18:30:02.027: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: got a TIMER 
event

Oct  3 18:30:02.027: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_handle_timers

Oct  3 18:30:02.027: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_handle_timers: managed 
timer expired 0x467BDFF8

HQ-RTR#
Oct  3 18:30:13.471: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
Oct  3 18:30:13.471: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_arq: 
arqp=0x48FFA888,crv=0x8, answerCall=0
Oct  3 18:30:13.471: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_sep_arq: ARQ 
Didn't use GK_AAA_PROC
Oct  3 18:30:13.471: //9FCEDD5F8059/9FCF7987805B/GK/gk_dns_query: No Name 
servers
Oct  3 18:30:13.475: //9FCEDD5F8059/9FCF7987805B/GK/rassrv_get_addrinfo: 
(1#5002) Matched tech-prefix 1#
Oct  3 18:30:13.475: //9FCEDD5F8059/9FCF7987805B/GK/rassrv_get_addrinfo: 
(1#5002) Matched zone prefix 5 and remainder 002
Oct  3 18:30:13.475: 
//xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_get_ingress_network: ARQ non-std 
ingress network = 3
Oct  3 18:30:13.475: //9FCEDD5F8059/9FCF7987805B/GK/rassrv_arq_select_viazone: 
about to check the destination side, dst_zonep=0x49005C44
Oct  3 18:30:13.475: //9FCEDD5F8059/9FCF7987805B/GK/rassrv_arq_select_viazone: 
matched zone is HQ, and z_outvianamelen=0
Oct  3 18:
HQ-RTR#30:13.475: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_get_ingress_network: 
ARQ non-std ingress network = 3
Oct  3 18:30:13.495: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
Oct  3 18:30:13.495: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_arq: 
arqp=0x4900B90C,crv=0x8008, answerCall=1
Oct  3 18:30:13.495: //9FCEDD5F8059/9FCF7987805B/GK/gk_rassrv_dep_arq: ARQ 
Didn't use GK_AAA_PROC
Oct  3 18:30:13.539: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
Oct  3 18:30:13.543: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_rassrv_arq: 
arqp=0x4900B90C,crv=0x8009, answerCall=1
Oct  3 18:30:13.543: //9FCEDD5F8059/9FCF7987805B/GK/gk_rassrv_dep_arq: ARQ 
Didn't use GK_AAA_PROC
Oct  3 18:30:13.555: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
HQ-RTR#
Oct  3 18:30:17.027: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: got a TIMER 
event

Oct  3 18:30:17.027: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_handle_timers

Oct  3 18:30:17.027: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_handle_timers: managed 
timer expired 0x467BDFF8

HQ-RTR#
Oct  3 18:30:19.519: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
Oct  3 18:30:19.567: //xxxxxxxxxxxx/xxxxxxxxxxxx/GK/gk_process: QUEUE_EVENT 
(minor 0) wakeup
HQ-RTR#undebug all
All possible debugging has been turned off
HQ-RTR#

_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to