Re: [OSL | CCIE_Voice] Gatekeeper registration questions
Thanks so much Scott. I does appear that CUBE is what dictates gw reg type. Very much appreciated. Paul (#16842 RS/Sec) From: scott carruthers [mailto:scarruthe...@hotmail.com] Sent: Thursday, March 25, 2010 10:35 PM To: Paul Dardinski; ccie_voice@onlinestudylist.com Subject: RE: [OSL | CCIE_Voice] Gatekeeper registration questions Paul, I haven't played around with forcing the output Type to either VOIP-GW or H323-GW much - but are you sure that your attempts is not backwards? In other words - I had the site C GW configured as a CUBE/with allow-connections configured and my gatekeeper output looked like: GATEKEEPER ENDPOINT REGISTRATION CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags --- - --- - - - 10.10.110.3 1720 10.10.110.3 60462 GKH323-GW E164-ID: 3001 E164-ID: 3002 E164-ID: 3999 H323-ID: CUCME Voice Capacity Max.= Avail.= Current.= 0 10.10.210.101720 10.10.210.1032885 GKVOIP-GW H323-ID: GK-Trunk_1 Voice Capacity Max.= Avail.= Current.= 0 10.10.210.111720 10.10.210.1132786 GKVOIP-GW H323-ID: GK-Trunk_2 Voice Capacity Max.= Avail.= Current.= 0 Total number of active registrations = 3 I removed the allow connection statements and my output changed to - this would seem to indicate the device will register as a VOIP-GW when it is not acting as a ip to ip GW: HQ-RTR#show gatek end GATEKEEPER ENDPOINT REGISTRATION CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags --- - --- - - - 10.10.110.3 1720 10.10.110.3 51687 GKVOIP-GW E164-ID: 3001 E164-ID: 3002 E164-ID: 3999 H323-ID: CUCME Voice Capacity Max.= Avail.= Current.= 0 10.10.210.101720 10.10.210.1032885 GKVOIP-GW H323-ID: GK-Trunk_1 Voice Capacity Max.= Avail.= Current.= 0 10.10.210.111720 10.10.210.1132786 GKVOIP-GW H323-ID: GK-Trunk_2 Voice Capacity Max.= Avail.= Current.= 0 Total number of active registrations = 3 Date: Thu, 25 Mar 2010 12:57:37 -0400 From: pa...@marshallcomm.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Gatekeeper registration questions All, Can anyone explain the core of how a gateway registration is recorded with the sh gatek endp command. Normally, as I understand it, a full H323 gw will register to a gk as type H323-GW, whereas the UCM will register as VOIP-GW. However, I'm running into a situation where no matter what I do my BR2 endpoint is registering with the HQ gk as VOIP-GW. I found reference elsewhere to a 323gw will register as voip-gw if it is configured as a CUBE. In this case though it isn't configured as a CUBE. I've put the pertinent VERY basic commands below. What I'm really looking for is some clarification on the different types and why they register differently if possible. Thanks for any help, Paul (#16842 RS/Sec) HQ-RTR#sh run | s gatekeeper gatekeeper zone local HQ ipexpert.com 10.10.110.1 no shutdown HQ-RTR#sh gatek end GATEKEEPER ENDPOINT REGISTRATION CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags --- - --- - - - 10.10.110.3 1720 10.10.110.3 65184 HQVOIP-GW E164-ID: 3102 H323-ID: BR2-RTR Voice Capacity Max.= Avail.= Current.= 0 10.1.200.20 48779 10.1.200.20 32824 HQVOIP-GW H323-ID: HQgk_1 Voice Capacity Max.= Avail.= Current.= 0 10.1.200.21 37078 10.1.200.21 32849 HQVOIP-GW H323-ID: HQgk_2 Voice Capacity Max.= Avail.= Current.= 0 Total number of active registratio BR2-RTRen BR2-RTR#sh run int Loop0 Building configuration... Current configuration : 163 bytes ! interface Loopback0 ip address 10.10.110.3 255.255.255.255 ip ospf network point-to-point h323-gateway voip interface h323-gateway voip h323-id BR2-RTR end BR2-RTR#sh gateway H.323 ITU-T Version: 4.0 H323 Stack Version: 0.1 H.323 service is up Gateway BR2-RTR is registered to Gatekeeper HQ Alias list (CLI configured) E164-ID 3102 H323-ID BR2-RTR Alias list (last RCF) E164-ID 3102 H323-ID BR2-RTR H323 resource thresholding is Disabled BR2-RTR# BR2-RTR#sh run | s voice service voice service voip The New Busy is not the old busy. Search, chat and e-mail from your inbox. Get started. http://www.windowslive.com/campaign/thenewbusy
[OSL | CCIE_Voice] Gatekeeper registration questions
All, Can anyone explain the core of how a gateway registration is recorded with the sh gatek endp command. Normally, as I understand it, a full H323 gw will register to a gk as type H323-GW, whereas the UCM will register as VOIP-GW. However, I'm running into a situation where no matter what I do my BR2 endpoint is registering with the HQ gk as VOIP-GW. I found reference elsewhere to a 323gw will register as voip-gw if it is configured as a CUBE. In this case though it isn't configured as a CUBE. I've put the pertinent VERY basic commands below. What I'm really looking for is some clarification on the different types and why they register differently if possible. Thanks for any help, Paul (#16842 RS/Sec) HQ-RTR#sh run | s gatekeeper gatekeeper zone local HQ ipexpert.com 10.10.110.1 no shutdown HQ-RTR#sh gatek end GATEKEEPER ENDPOINT REGISTRATION CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags --- - --- - - - 10.10.110.3 1720 10.10.110.3 65184 HQVOIP-GW E164-ID: 3102 H323-ID: BR2-RTR Voice Capacity Max.= Avail.= Current.= 0 10.1.200.20 48779 10.1.200.20 32824 HQVOIP-GW H323-ID: HQgk_1 Voice Capacity Max.= Avail.= Current.= 0 10.1.200.21 37078 10.1.200.21 32849 HQVOIP-GW H323-ID: HQgk_2 Voice Capacity Max.= Avail.= Current.= 0 Total number of active registratio BR2-RTRen BR2-RTR#sh run int Loop0 Building configuration... Current configuration : 163 bytes ! interface Loopback0 ip address 10.10.110.3 255.255.255.255 ip ospf network point-to-point h323-gateway voip interface h323-gateway voip h323-id BR2-RTR end BR2-RTR#sh gateway H.323 ITU-T Version: 4.0 H323 Stack Version: 0.1 H.323 service is up Gateway BR2-RTR is registered to Gatekeeper HQ Alias list (CLI configured) E164-ID 3102 H323-ID BR2-RTR Alias list (last RCF) E164-ID 3102 H323-ID BR2-RTR H323 resource thresholding is Disabled BR2-RTR# BR2-RTR#sh run | s voice service voice service voip ___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
Re: [OSL | CCIE_Voice] Gatekeeper registration questions
Paul, I haven't played around with forcing the output Type to either VOIP-GW or H323-GW much - but are you sure that your attempts is not backwards? In other words - I had the site C GW configured as a CUBE/with allow-connections configured and my gatekeeper output looked like: GATEKEEPER ENDPOINT REGISTRATION CallSignalAddr Port RASSignalAddr Port Zone Name TypeFlags --- - --- - - - 10.10.110.3 1720 10.10.110.3 60462 GKH323-GW E164-ID: 3001 E164-ID: 3002 E164-ID: 3999 H323-ID: CUCME Voice Capacity Max.= Avail.= Current.= 0 10.10.210.101720 10.10.210.1032885 GKVOIP-GW H323-ID: GK-Trunk_1 Voice Capacity Max.= Avail.= Current.= 0 10.10.210.111720 10.10.210.1132786 GKVOIP-GW H323-ID: GK-Trunk_2 Voice Capacity Max.= Avail.= Current.= 0 Total number of active registrations = 3 I removed the allow connection statements and my output changed to - this would seem to indicate the device will register as a VOIP-GW when it is not acting as a ip to ip GW: HQ-RTR#show gatek end GATEKEEPER ENDPOINT REGISTRATION CallSignalAddr Port RASSignalAddr Port Zone Name TypeFlags --- - --- - - - 10.10.110.3 1720 10.10.110.3 51687 GKVOIP-GW E164-ID: 3001 E164-ID: 3002 E164-ID: 3999 H323-ID: CUCME Voice Capacity Max.= Avail.= Current.= 0 10.10.210.101720 10.10.210.1032885 GKVOIP-GW H323-ID: GK-Trunk_1 Voice Capacity Max.= Avail.= Current.= 0 10.10.210.111720 10.10.210.1132786 GKVOIP-GW H323-ID: GK-Trunk_2 Voice Capacity Max.= Avail.= Current.= 0 Total number of active registrations = 3 Date: Thu, 25 Mar 2010 12:57:37 -0400 From: pa...@marshallcomm.com To: ccie_voice@onlinestudylist.com Subject: [OSL | CCIE_Voice] Gatekeeper registration questions All, Can anyone explain the core of how a gateway registration is recorded with the “sh gatek endp” command. Normally, as I understand it, a full H323 gw will register to a gk as type “H323-GW”, whereas the UCM will register as “VOIP-GW”. However, I’m running into a situation where no matter what I do my BR2 endpoint is registering with the HQ gk as VOIP-GW. I found reference elsewhere to a 323gw will register as voip-gw if it is configured as a CUBE. In this case though it isn’t configured as a CUBE. I’ve put the pertinent VERY basic commands below. What I’m really looking for is some clarification on the different types and why they register differently if possible. Thanks for any help, Paul (#16842 RS/Sec) HQ-RTR#sh run | s gatekeeper gatekeeper zone local HQ ipexpert.com 10.10.110.1 no shutdown HQ-RTR#sh gatek end GATEKEEPER ENDPOINT REGISTRATION CallSignalAddr Port RASSignalAddr Port Zone Name TypeFlags --- - --- - - - 10.10.110.3 1720 10.10.110.3 65184 HQ VOIP-GW E164-ID: 3102 H323-ID: BR2-RTR Voice Capacity Max.= Avail.= Current.= 0 10.1.200.20 48779 10.1.200.20 32824 HQ VOIP-GW H323-ID: HQgk_1 Voice Capacity Max.= Avail.= Current.= 0 10.1.200.21 37078 10.1.200.21 32849 HQ VOIP-GW H323-ID: HQgk_2 Voice Capacity Max.= Avail.= Current.= 0 Total number of active registratio BR2-RTRen BR2-RTR#sh run int Loop0 Building configuration... Current configuration : 163 bytes ! interface Loopback0 ip address 10.10.110.3 255.255.255.255 ip ospf network point-to-point h323-gateway voip interface h323-gateway voip h323-id BR2-RTR end BR2-RTR#sh gateway H.323 ITU-T Version: 4.0 H323 Stack Version: 0.1 H.323 service is up Gateway BR2-RTR is registered to Gatekeeper HQ Alias list (CLI configured) E164-ID 3102 H323-ID BR2-RTR Alias list (last RCF) E164-ID 3102 H323-ID BR2-RTR H323 resource thresholding is Disabled BR2-RTR# BR2-RTR#sh run | s voice service voice service voip _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_3___ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
