[cisco-voip] H323 call routing via GK

Davis, Michael Michael_Davis at eLoyalty.com
Tue Jan 17 16:15:57 EST 2006


Just a clarification 'cause I'm not sure I was clear:  you should choose option A, B, OR, C for handling the 1# prefix.
 
Michael

	-----Original Message----- 
	From: Davis, Michael 
	Sent: Tue 1/17/2006 3:13 PM 
	To: Robin H; cisco-voip at puck.nether.net 
	Cc: 
	Subject: RE: [cisco-voip] H323 call routing via GK
	
	
	Hi Robin,
	 
	You are on the right track.  But one assumption is not correct.  Callmanager (JKT) will not recognize 1# as the tech-prefix and strip the 1# from the inbound call.  You need to either a) strip it with a translation pattern, b) set significant digits 8 c) include 1# in the outbound route-pattern and strip it with the 9 before dialing PSTN.  Basically, treat 1# as you would any other extraneous digits.
	 
	HTH,
	Michael

		-----Original Message----- 
		From: cisco-voip-bounces at puck.nether.net on behalf of Robin H 
		Sent: Mon 1/16/2006 1:22 AM 
		To: cisco-voip at puck.nether.net 
		Cc: 
		Subject: Re: [cisco-voip] H323 call routing via GK
		
		

		Here is my dial plan config on CME router (Note that I have updated
		some config) :
		!
		translation-rule 1
		 rule 1 ^90016221 9 (updated)
		!
		dial-peer voice 1 pots
		 incoming-called-number .
		 direct-inward-dial
		!
		dial-peer voice 2 pots
		 destination-pattern 90016221.......
		 direct-inward-dial
		 preference 1
		 port 2/0:15
		!
		dial-peer voice 3 pots
		 destination-pattern 9T
		 direct-inward-dial
		 port 2/0:15
		!
		dial-peer voice 23 voip
		 destination-pattern 90016221.......
		 translate-outgoing called 1
		 session target ras
		 tech-prefix 1# (added)
		 dtmf-relay h245-alphanumeric
		 no vad
		!
		GateKeeper config:
		====================
		Zone local xxxx test.com 172.16.12.254
		Zone prefix xxxx 28.. gw-priority 10 JKT_1
		Zone prefix xxxx 28.. gw-priority 5 JKT_2
		Zone prefix xxxx 11.. gw-priority 10 BDG
		Zone prefix xxxx 9....... gw-priority 10 JKT_1 (updated)
		Zone prefix xxxx 9....... gw-priority 5 JKT_2  (updated)
		Gw-type-prefix 1#
		Bandwidth total zone xxxx 64
		
		I would like ask:
		- With the dial-peer voice 23, when I dialed "90016221XXXXXXX" from
		CME site, the digits sent to GK will be "1#9XXXXXXX". The GK will have
		a match ie:
		4w2d: rassrv_get_addrinfo: (1#96694456) Matched tech-prefix 1#
		4w2d: rassrv_get_addrinfo: (1#96694456) Matched zone prefix 9 and
		remainder 6694456
		
		>From this point, I assume the digits sent to CallManager will be
		1#96694456 (plz correct me if I am wrong),
		and it will strip tech prefix 1# and then CallManager will try to
		match with its dial patterns. I have configured dial-pattern of
		- 9.[1-9]XXXXXX with predot discard digit route to local gateway
		
		The gatekeeeper controlled trunk has parameters under Inbound Calls:
		- Significant Digits = All (Updated)
		- CSS = HQ-all
		
		All direct PSTN and 4 digit dialing calls are fine. Only calls that
		are routed to CME router from remote site always failed. Anything that
		I missed?
		
		Hi Kevin,
		I have changed the translation rule as well but the resutl still same. thanks
		
		
		
		On 1/16/06, Kevin Thorngren <kthorngr at cisco.com> wrote:
		> You might need to change your Translation Rule to this:
		> translation-rule 1
		>  rule 1 ^90016221……. 6221
		>
		> Please refer to this page for more info on Translation Rules:
		> http://www.cisco.com/en/US/partner/tech/tk652/tk90/
		> technologies_configuration_example09186a0080094681.shtml
		>
		> Kevin
		>
		> On Jan 15, 2006, at 7:21 AM, Robin H wrote:
		>
		> > I have one voice gateway running H323 and another gateway is running
		> > CME. I want to save IDD cost with toll bypass but having problem with
		> > call routing via gatekeeper.
		> >
		> > Route-pattern config at CallManager:
		> > 28XX -> route to gatekeeper
		> > 11XX -> route to gatekeeper
		> >
		> >  GK config:
		> >  Zone local xxxx test.com 172.16.12.254
		> >  Zone prefix xxxx 28.. gw-priority 10 JKT_1
		> >  Zone prefix xxxx 28.. gw-priority 5 JKT_2
		> >  Zone prefix xxxx 11.. gw-priority 10 BDG
		> >  Zone prefix xxxx 6221……. gw-priority 10 JKT_1
		> >  Zone prefix xxxx 6221……. gw-priority 5 JKT_2
		> >  Gw-type-prefix 1#
		> >  Bandwidth total zone xxxx 64
		> >
		> > config at BDG router (CME):
		> > translation-rule 1
		> >  rule 1 ^90016221 6221
		> > !
		> > dial-peer voice 23 voip
		> >  destination-pattern 90016221…….
		> >  translate-outgoing called 1
		> >  session target ras
		> >  dtmf-relay h245-alphanumeric
		> >  no vad
		> > =========================
		> >
		> > Info:
		> > 28XX is the extension in JKT site
		> > 11XX is the ext in BDG site running CME 3.2
		> > JKT and BDG gateways are registered as H323 devices in CM 3.3 with
		> > significant-digits = 4.
		> >
		> >
		> > Dial Test from BDG:
		> > -         Dial 28XX is working fine
		> > -         Dial 11XX is working fine
		> > -         Dial to 90016221XXXXXXX (toll bypass) always failed.
		> >
		> > Plz enlighten me. thanks
		> >
		> > _______________________________________________
		> > cisco-voip mailing list
		> > cisco-voip at puck.nether.net
		> > https://puck.nether.net/mailman/listinfo/cisco-voip
		> >
		>
		>
		
		_______________________________________________
		cisco-voip mailing list
		cisco-voip at puck.nether.net
		https://puck.nether.net/mailman/listinfo/cisco-voip
		




More information about the cisco-voip mailing list