Thanks everyone for your kind inputs..I will try in my next lab and sorry fro delayed response as I got busy with work.
--- On Fri, 3/27/09, CCIE OSL <ccie...@gmail.com> wrote: From: CCIE OSL <ccie...@gmail.com> Subject: Re: [OSL | CCIE_Voice] CME- Re-route the call when we somehowrejectthe call from GK To: "Alex" <alex.arsen...@gmail.com> Cc: ccie_voice@onlinestudylist.com, "anil batra" <anil...@yahoo.com> Date: Friday, March 27, 2009, 7:35 PM Thanks.. I will lab it up and try it. /Jin Jung... Alex wrote: > AFAIK, tech-prefix cannot contain wildcards. > So to use static mapping you have to either: > 1/ map every unwanted full DN on GK to a nonexistent IP@ > 2/ figure out whether your unwanted DN start with common digit string and > configure shorter tech-prefix(es). Example: > Unwanted DNs are 12122216666, 12122216777, 12122218766, 12122218745. Then > configure the following: > ! > gatekeeper > gw-type-prefix 12122216 gw ipaddr <nonexistent IP@> > gw-type-prefix 121222187 gw ipaddr <nonexistent IP@> > ! > To make sure you did not blackhole the rest of DNs in the 12122216XXX range, > prepend them with CCM tech-prefix (e.g. 2#) when sending ARQ to the GK. > And don't prepend the 12122216666 and 12122216777 when sending ARQ to GK. Use > specific CME dialpeers to achieve that: > ! > dial-peer voice voi 12126 voip > destination-pattern 12122216[67][67][67] > sess target ras > ! > dial-peer voice voi 1212 voip > destination-pattern 12122216... > sess target ras > tech-prefix 2# > ! > I don't have the lab handy to test this. Would you be able to help? > Rgds > Alex > > > > ----- Original Message ----- From: "CCIE OSL" <ccie...@gmail.com> > To: "Alex" <alex.arsen...@gmail.com> > Cc: "anil batra" <anil...@yahoo.com>; <ccie_voice@onlinestudylist.com> > Sent: Friday, March 27, 2009 1:14 PM > Subject: Re: [OSL | CCIE_Voice] CME- Re-route the call when we > somehowrejectthe call from GK > > >> Hi Alex, >> But that seems like its for only for one DN, Do you think this will work >> for say 1212222....? >> >> I guess, prefix will be 12122222, >> >> I am trying to make similar concept work, >> I was trying Hop-off prefix . I guess this is same thing. >> >> Did this work for you?? >> >> And I guess, this will work for reverse direction as well, if we were to >> make a call from HQ to BR2. >> >> >> >> Alex wrote: >>> AFAIK, the simplest way would be to configure static mapping on gatekeeper: >>> ! >>> gatekeeper >>> gw-type-prefix 12122216666 gw ipaddr <nonexisting GW IP@> >>> ! >>> Then for a DNIS == 12122216666 the GK will return nonexisting i...@. >>> Remember, there is no fixed separator between tech-prefix and E.164 number, >>> so the whole DNIS == 12122216666 will be regarded as tech-prefix. >>> CME will exhaust its H.225 SETUP timeout (15 secs by default) towards >>> nonexisting IP@ and fall back to PSTN dialpeer. >>> To make it faster, configure voice class h323 on CME: >>> ! >>> voice class h323 1 >>> h225 timeout setup 3 >>> h225 timeout tcp establish 3 >>> ! >>> and of course assign this voice class to outbound CME dialpeer. >>> All other DNIS should go through assuming you configure and register >>> shorter tech-prefix on called side (I assume it's CCM). >>> Rgds >>> Alex >>> >>> ----- Original Message ----- >>> *From:* anil batra <mailto:anil...@yahoo.com> >>> *To:* ccie_voice@onlinestudylist.com >>> <mailto:ccie_voice@onlinestudylist.com> ; Cliff McGlamry >>> <mailto:cl...@mcglamry.net> >>> *Sent:* Friday, March 27, 2009 3:59 AM >>> *Subject:* Re: [OSL | CCIE_Voice] CME- Re-route the call when we >>> somehowrejectthe call from GK >>> >>> Cliff, I have calls going thru HQ to CME and vice versa via GK. So >>> no issues at all. >>> >>> Now I want to know if there is somehow I can do something on GK( >>> without shut down or CAC) to reject the call so that call from CME >>> will go thru PSTN >>> >>> Hope I myself clear this time :) >>> >>> --- On *Fri, 3/27/09, Cliff McGlamry /<cl...@mcglamry.net >>> <mailto:cl...@mcglamry.net>>/* wrote: >>> >>> >>> From: Cliff McGlamry <cl...@mcglamry.net >>> <mailto:cl...@mcglamry.net>> >>> Subject: Re: [OSL | CCIE_Voice] CME- Re-route the call when we >>> somehow rejectthe call from GK >>> To: "anil batra" <anil...@yahoo.com>, >>> ccie_vo...@onlinestudylist.com >>> Date: Friday, March 27, 2009, 8:13 AM >>> >>> Anil, >>> Sorry, but I don't understand your question. I'll try to >>> expand a little since that's what it appears you are looking for. >>> IF everything is perfectly configured and it still doesn't >>> work, then one of the following may be required: >>> Restart of CCM Service (both servers) >>> Verify Transcoders are UP and in the correct LOCATION and MRGL >>> (if they are up but put in the wrong locations, things break. I've >>>had this happen, and it's maddening to find!). >>> You may possibly need to reboot CME. >>> Make sure gatekeeper has been issued a NO SHUT. Sounds dumb, >>> but it actually is a problem quite often. Cliff >>> >>> ----- Original Message ----- >>> *From:* anil batra </mc/compose?to=anil...@yahoo.com> >>> *To:* ccie_voice@onlinestudylist.com >>> </mc/compose?to=ccie_vo...@onlinestudylist.com> ; Cliff >>> McGlamry </mc/compose?to=cl...@mcglamry.net> >>> *Sent:* Thursday, March 26, 2009 10:20 PM >>> *Subject:* Re: [OSL | CCIE_Voice] CME- Re-route the call >>> when we somehow rejectthe call from GK >>> >>> Hi Cliff, >>> >>> Thanks for your kind response. I don't have any confi with >>> me but what I am sayign is if you supposedly I have >>> everything working that is Calls passing to and from HQ to >>> CME via GK. But now I suddenly want the scenario I >>> discussed in my last mail...how to achive that please.. >>> >>> --- On *Fri, 3/27/09, Cliff McGlamry /<cl...@mcglamry.net >>> </mc/compose?to=cl...@mcglamry.net>>/* wrote: >>> >>> >>> From: Cliff McGlamry <cl...@mcglamry.net >>> </mc/compose?to=cl...@mcglamry.net>> >>> Subject: Re: [OSL | CCIE_Voice] CME- Re-route the call >>> when we somehow rejectthe call from GK >>> To: "anil batra" <anil...@yahoo.com>, >>> ccie_vo...@onlinestudylist.com >>> Date: Friday, March 27, 2009, 7:47 AM >>> >>> Several things. >>> 1. Either you're missing something in the gatekeeper >>> config call routing wise >>> 2. You're missing something in the CallManager config >>> call routing wise >>> 3. You're missing something on CME call routing wise >>> 4. You have a codec mismatch and/or you don't have >>> transcode resources available where required >>> 5. You have a problem with locations bandwidth on CCM >>> 6. You need an MTP and don't have it configured. >>> If you want a more specific answer, start by posting >>> your gatekeeper config and the output trace of: >>> debug gatekeeper main 10 >>> debug gatekeeper call 10 >>> These should serve to isolate whether the issue is >>> before or after the gatekeeper. >>> Cliff >>> >>> ----- Original Message ----- >>> *From:* anil batra >>> *To:* ccie_voice@onlinestudylist.com >>> *Sent:* Thursday, March 26, 2009 8:59 PM >>> *Subject:* [OSL | CCIE_Voice] CME- Re-route the >>> call when we somehow rejectthe call from GK >>> >>> How can we have a call fail even though there is >>> ample amount of BW avilable via GK ( no CAC >>> restriction) and there is proper TP, ZP etc >>> defined on GK and everywhere. I mean with all the >>> requried configs in place if I want to call HQ >>> Phone via GK but GK should reject the call and the >>> call be routed out local CME GW. >>> >>> >>> >>> >> >
