Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

TEHO with a Gatekeeper

Can someone give me a config example or short explnation of how this can be done? I am still a little fuzzy as to how to process what digits in a route pattern that should be passed to the Gatekeeper?


Hall of Fame Super Silver

Re: TEHO with a Gatekeeper

Well, it all depends on what you really want to do, where are you hoping off, is it another CCM cluster, a GW, CME?

Typically you will send all digits to the GK with or without the off-net access code (remember to prefix tech-prefix on the route list or RP, unless you are going to use default tech-prefix) and then simply use zone prefix to direct the call to desired location. For example assume you have CM and CME and you would like to hop-off from CM out of CME GW, so when user CM 1 dials 9.011485551234 it needs to go via GK out CME GW, you would have following config:

zone local HQ

zone local CME

zone prefix CME 9011*

no shut

On the CME GW, you might want to manipulate the incoming digits to strip the 01148, so the call goes out as a local call, to do that one way is to use translation rule as following:

voice translation-rule 1

rule 1 /^1#901148/ //

voice translation-profile 1

translate called 1

dial-peer voice 1 voip

incoming called-number 1#9011T

translation-profile incoming 1

The 1# is the tech-prefix which was prefixed on the CCM, and which CME registers with.



Re: TEHO with a Gatekeeper


A few rules to keep in mind.

a. If e164 registrations from a gateway is allowed, you dont need tech-prefix or zone prefix to route calls to that gateway. (As long as the dialed digit matches one of the e164 numbers)

b. If a call need to be sent to a gateway from which e164 registrations are not allowed, you will need to use zone prefix and/or combination of tech prefix to route the call depending upon whether the zones are local or remote.

c. For remote zones always use a remote zone prefix to send the call to other gatekeeper. No need to use tech prefix here.

d. if there are multiple gateways registering to a gatekeeper in the same zone, then you will need to use a combination of zone prefix and tech prefix to route the call to gateways in that zone.

e. if there is an IPIPGW involved in the mix along with a gatekeeper, make sure that you have outvia keyword specified in the target zone to which calls need to be routed, but need to go through the gatekeeper/IPIPGW combination.

Any gatekeeper routing scenario can be fit into and summarized using the flowcharts provided in this link. I would suggest that you use the flowcharts as a rule of thumb.

and yeah..when troubleshooting complex gatekeeper routing problems, your best friend is "Debug gatekepeer main 10".



PS: please remember to rate all posts!