I think what you mean that when you register E164 numbers - that you
can't configure a zone prefix until you shut the GK down - then
configure the zone prefix - then no shut - and then you surely can
have both Zone Prefixes and E164 numbers for the same zone - no issues.
--
Mark Snow
CCIE #14073 (Voice, Security)
CCSI #31583
Senior Technical Instructor - IPexpert, Inc.
A Cisco Learning Partner - We Accept Learning Credits!
Telephone: +1.810.326.1444
Fax: +1.309.413.4097
Mailto: [EMAIL PROTECTED]
--
Join our free online support and peer group communities:
http://www.IPexpert.com/communities
--
IPexpert - The Global Leader in Self-Study, Classroom-Based, Video-On-
Demand and Audio Certification Training Tools for the Cisco CCIE R&S
Lab, CCIE Security Lab, CCIE Service Provider Lab , CCIE Voice Lab and
CCIE Storage Lab Certifications.
--
On Mar 28, 2008, at 4:53 PM, John wrote:
When you register e164 number you can’t have zone prefixes. In
addition, your alias static has a 011 as the leading digits of the
pattern, but the debug here:
Mar 28 19:58:14.183: rassrv_get_addrinfo: (2#3313213333) unresolved
zone prefix,
Shows that you are sending the call without international dialing
prefix (011). One last thing, it doesn’t look as though you have an
e164 registered with a last 4 digits of 3333. If you did have an
extension of 3333, then it would have resolved with 3333 and
3313213333 and your call would go through (because it looks like
you’re doing dialplan pattern). What I would recommend is not
registering your e164s, then you can do zone prefixes and make the
call route the way you want to.
On a side note, it looks like you’re using dialplan pattern on your
CME from the E164 numbers that are registered. I don’t think that I
would be alone if I recommend against using this because of some of
the other issues that it can create.
Hope that helps.
John.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
] On Behalf Of Onur Tufekci
Sent: Friday, March 28, 2008 3:08 PM
To: Erin Mikelson
Cc: [email protected]
Subject: Re: [OSL | CCIE_Voice] GK and e164 register
Registering CME numbers to GK breaks the routing I believe. Try
without registering the cme numbers.
On Fri, Mar 28, 2008 at 4:04 PM, Erin Mikelson
<[EMAIL PROTECTED]> wrote:
I'm not working off a specific lab, but thought I would try to
create my own. But, of course, I'm stuck. And without an answer
guide, I'm not sure if what I'm doing is actually possible.
So, in going along with most of the labs, here is my scenario:
Gatekeeper with HQ-RTR and CME zones
no Default tech prefix. But I'm using 1# for HQ and 2# for CME
Do register e.164 numbers to GK from CME.
Call flow from HQ for international calls toward CME site, route
through GK and out the CME PSTN.
This is what I can't get to work.
With registering the e.164 addresses, I can't use a prefix on my
gatekeeper. So, I tried using the alias static command, but I can't
use it with a wildcard. Well, the config let me, but my debugs try
to send it toward my HQ site again.
So, is this scenario even possible? Or, would I have to use an
IPIPGW and/or another GK to send my calls out?
Here is partial config and debug.
-----------------
P1_HQ_RTR#
gatekeeper
zone local HQ-RTR ipexpert.com 172.1.100.1
zone local CME ipexpert.com
zone prefix HQ-RTR 1*
zone prefix HQ-RTR 2*
alias static 172.1.102.1 1720 gkid CME gateway voip ras 172.1.102.1
50130 e164 011331*
gw-type-prefix 1#* gw ipaddr 10.1.200.21 1720
gw-type-prefix 2#* gw ipaddr 172.1.102.1 1720
bandwidth remote 64
no shutdown
P1_HQ_RTR#sh gatek end
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name
Type Flags
--------------- ----- --------------- ----- ---------
---- -----
10.1.200.21 1720 10.1.200.21 1719 HQ-RTR
VOIP-GW
ENDPOINT-ID: 4755A99C00000002 VERSION: 2 AGE: 32 secs
SupportsAnnexE: FALSE
g_supp_prots: 0x00000050
H323-ID: HK_Trunk_1
Voice Capacity Max.= Avail.= Current.= 0
172.1.102.1 1720 172.1.102.1 50130 CME VOIP-GW
D S
ENDPOINT-ID: 4738A5F800000002 VERSION: 4 AGE: 23 secs
SupportsAnnexE: FALSE
g_supp_prots: 0x00000050
E164-ID: 011331 (static)
E164-ID: 3002
E164-ID: 3003
E164-ID: 3004
E164-ID: 3001
E164-ID: 3100
E164-ID: 3313213001
E164-ID: 3313213002
E164-ID: 3313213003
E164-ID: 3313213004
E164-ID: 3313213020
E164-ID: 3313213600
E164-ID: 3313213999
E164-ID: 3313213998
E164-ID: 3313213100
H323-ID: CME
Voice Capacity Max.= Avail.= Current.= 0
Total number of active registrations = 2
---------
CME
------------
interface Loopback0
ip address 172.1.102.1 255.255.255.255
ip ospf network point-to-point
h323-gateway voip interface
h323-gateway voip id CME ipaddr 172.1.100.1 1719
h323-gateway voip h323-id CME
h323-gateway voip tech-prefix 2#
h323-gateway voip bind srcaddr 172.1.102.1
-------------------------------
--------------------
P1_HQ_RTR#DEB GATEK MAIN 10
P1_HQ_RTR#
Mar 28 19:58:14.179: gk_process: QUEUE_EVENT (minor 0) wakeup
Mar 28 19:58:14.183: gk_rassrv_arq: arqp=0x46D60794, crv=0x20,
answerCall=0
Mar 28 19:58:14.183: gk_rassrv_sep_arq: ARQ Didn't use GK_AAA_PROC
Mar 28 19:58:14.183: gk_dns_query: No Name servers
Mar 28 19:58:14.183: rassrv_get_addrinfo: (2#3313213333) Matched
tech-prefix 2#
Mar 28 19:58:14.183: rassrv_get_addrinfo: (2#3313213333) unresolved
zone prefix,
using source zone HQ-RTR
Mar 28 19:58:14.183: gk_rassrv_get_ingress_network: returning
default ingress
network = 1
Mar 28 19:58:14.183: rassrv_arq_select_viazone: about to check the
source side,
src_zonep=0x46837238
P1_HQ_RTR#
Mar 28 19:58:14.183: rassrv_arq_select_viazone: matched zone is HQ-
RTR, and
z_invianamelen=0
Mar 28 19:58:14.183: rassrv_arq_select_viazone: about to check the
destination side,
dst_zonep=0x46837238
Mar 28 19:58:14.183: rassrv_arq_select_viazone: matched zone is HQ-
RTR, and
z_outvianamelen=0
Mar 28 19:58:14.183: gk_rassrv_get_ingress_network: returning
default ingress
network = 1
Mar 28 19:58:14.183: rassrv_get_addrinfo: (2#3313213333) tech-prefix
gateway
selection failed.
Mar 28 19:58:14.183: gk_rassrv_sep_arq: rassrv_get_addrinfo() failed
(return code =
0x107)
P1_HQ_RTR#
Thanks!
Erin
How well do you know your celebrity gossip? Talk celebrity
smackdowns here.