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

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

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

GK callrouting issue

We have good the routing, acl, trunk configuration (90% sure), but still getting fast busy tone, I am using tech-prefix 1#* on Callmanager , is it correct?

I am dialing 33861 , why it is showed on the debug like this ( 33 and remainder 861)

GK#

Aug 20 23:16:32.424: gk_rassrv_arq: arqp=0x46FEF1CC, crv=0x3, answerCall=0

Aug 20 23:16:32.424: gk_dns_query: No Name servers

Aug 20 23:16:32.424: rassrv_get_addrinfo: (33861) Tech-prefix match failed.

Aug 20 23:16:32.424: rassrv_get_addrinfo: (33861) Matched zone prefix 33 and remainder 861

Aug 20 23:16:32.424: rassrv_arq_select_viazone: about to check the source side, src_zonep=0x47027754

Aug 20 23:16:32.424: rassrv_arq_select_viazone: matched zone is SGO_CCM, and z_invianamelen=0

Aug 20 23:16:32.424: rassrv_arq_select_viazone: about to check the destination side, dst_zonep=0x46F7E530

Any guide will help me..

Thxs

Andres

2 ACCEPTED SOLUTIONS

Accepted Solutions
Hall of Fame Super Silver

Re: GK callrouting issue

How is your GK trunk configured on CM, is it configured to strip 1#, the tech prefix will in fact be delivered to CM.

Chris

VIP Super Bronze

Re: GK callrouting issue

Hi,

So what is happening is this...You have configured a tech-prifix of 1#* but when you dial your number you have not included 1#. There is no way thegk will match the prefix if your calling number does not include the prefix.

So you will need to send a digit like 1#33.. for the gatekeeper to route the callto CCM

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
5 REPLIES
Hall of Fame Super Silver

Re: GK callrouting issue

How is your GK trunk configured on CM, is it configured to strip 1#, the tech prefix will in fact be delivered to CM.

Chris

New Member

Re: GK callrouting issue

Technology Prefix 1#*

VIP Super Bronze

Re: GK callrouting issue

The debug output indicates that no tech prefix is matched.

Can you post your full GK config here

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Re: GK callrouting issue

!

gatekeeper

zone local ALNGATE01 acme.com X.X.X.X enable-intrazone

zone local CVP acme.com enable-intrazone

zone local MCK_CCM acme.com

zone local SCH_CCM acme.com

zone local CMS_CCM acme.com

zone local SCH_ALN acme.com enable-intrazone

zone local CMS_ALN acme.com enable-intrazone

zone local SGO_CCM acme.com

zone local SGO_ALN acme.com enable-intrazone

zone local ALN_CCM acme.com

zone prefix MCK_CCM 20... gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 21... gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 22... gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 23... gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 24... gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 25... gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 260.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 261.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 262.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 263.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 264.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 265.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix CMS_CCM 267.. gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix MCK_CCM 268.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 269.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 27... gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 280.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 281.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 282.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix CMS_CCM 2837. gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix CMS_CCM 2838. gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix CMS_CCM 2839. gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix MCK_CCM 283.. gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix MCK_CCM 29... gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix ALN_CCM 33... gw-priority 10 ALN2MCK_GATEKEEPER_1

zone prefix MCK_CCM 34... gw-priority 10 MCK2MCK_GATEKEEPER_1

zone prefix ALN_CCM 350.. gw-priority 10 ALN2MCK_GATEKEEPER_1

zone prefix ALN_CCM 351.. gw-priority 10 ALN2MCK_GATEKEEPER_1

zone prefix ALN_CCM 352.. gw-priority 10 ALN2MCK_GATEKEEPER_1

zone prefix ALN_CCM 353.. gw-priority 10 ALN2MCK_GATEKEEPER_1

zone prefix ALN_CCM 358.. gw-priority 10 ALN2MCK_GATEKEEPER_1

zone prefix ALN_CCM 359.. gw-priority 10 ALN2MCK_GATEKEEPER_1

zone prefix CVP 38* gw-priority 10 alncccvp1

zone prefix CVP 38* gw-priority 5 MCKCCCVP1

zone prefix SGO_CCM 450.. gw-priority 10 SGO2MCK_GATEKEEPER_1

zone prefix SGO_CCM 451.. gw-priority 10 SGO2MCK_GATEKEEPER_1

zone prefix SGO_CCM 452.. gw-priority 10 SGO2MCK_GATEKEEPER_1

zone prefix SGO_CCM 453.. gw-priority 10 SGO2MCK_GATEKEEPER_1

zone prefix SGO_CCM 454.. gw-priority 10 SGO2MCK_GATEKEEPER_1

zone prefix SCH_CCM 63... gw-priority 10 SCH2MCK_GATEKEEPER_1

zone prefix SCH_CCM 64... gw-priority 10 SCH2MCK_GATEKEEPER_1

zone prefix SCH_CCM 65... gw-priority 10 SCH2MCK_GATEKEEPER_1

zone prefix SCH_CCM 66... gw-priority 10 SCH2MCK_GATEKEEPER_1

zone prefix SCH_CCM 68... gw-priority 10 SCH2MCK_GATEKEEPER_1

zone prefix SCH_CCM 6* gw-priority 10 SCH2MCK_GATEKEEPER_1

zone prefix CMS_CCM 81... gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix CMS_CCM 82... gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix CMS_CCM 83... gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix CMS_CCM 84... gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix CMS_CCM 85... gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix CMS_CCM 87... gw-priority 10 CMS2MCK_GATEKEEPER_1

zone prefix CMS_CCM 8* gw-priority 10 CMS2MCK_GATEKEEPER_1

arq reject-unknown-prefix

bandwidth total default 1024

no shutdown

VIP Super Bronze

Re: GK callrouting issue

Hi,

So what is happening is this...You have configured a tech-prifix of 1#* but when you dial your number you have not included 1#. There is no way thegk will match the prefix if your calling number does not include the prefix.

So you will need to send a digit like 1#33.. for the gatekeeper to route the callto CCM

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
149
Views
0
Helpful
5
Replies