Click on link to enlarge the pic.
Archive for the ‘Gatekeeper’ Category
7
How to trigger via zone behaviour?
Local zones – always enable outvia on the destination zone
Remote zones – use invia or outvia on the remote zone
Via-zone gatekeepers differ from legacy gatekeepers in how LRQ and ARQ messages are used for call routing. Using via-zone gatekeepers will maintain normal clusters and functionality. Legacy gatekeepers examine incoming LRQs based on the called number, and more specifically the dialedDigits field in the destinationInfo portion of the LRQ. Via-zone gatekeepers look at the origination point of the LRQ before looking at the called number. If an LRQ comes from a gatekeeper listed in the via-zone gatekeeper’s remote zone configurations, the gatekeeper checks to see that the zone remote configuration contains an invia or outvia keyword. If the configuration contains these keywords, the gatekeeper uses the new via-zone behavior; if not, it uses legacy behavior.
For ARQ messages, the gatekeeper determines if an outvia keyword is configured on the destination zone. If the outvia keyword is configured, and the zone named with the outvia keyword is local to the gatekeeper, the call is directed to a Cisco Multiservice IP-to-IP Gateway in that zone by returning an ACF pointing to the Cisco Multiservice IP-to-IP Gateway. If the zone named with the outvia keyword is remote, the gatekeeper sends a location request to the outvia gatekeeper rather than the remote zone gatekeeper. The invia keyword is not used in processing the ARQ.
When using IPIPGW, you need to define a zone prefix to route calls. invia zones does not use the default technology.
If you have two gatekeeper trunks, one in a G711 region and the other in a G729 region and you setup the Route list with G711 as the first priority and G729 as the second priority and the gatekeeper does not have enough bandwidth to process a G711 call, then it will fallback and use the G729 trunk to process the call.
You do not need to enable BRQ to make this happen.
For a gateway to register with a gatekeeper, there should be at least one voip dial-peer defined in the gateway.
If it is a CME router, then when you define ephones, that will create dial-peer and hence that will work fine.
Issues with gatekeeper zone prefix and end point registration
Posted: July 30, 2006 by cciestudy in GatekeeperIf you define a zone prefix for a local zone , then it will prevent gateways from registering using E.164 ID to that zone.
zone local zone10 aaa.com 10.1.1.1
zone prefix zone10 5000
With this configuration, none of the gateways can register to zone10 using E.164 ID’s.
How to network Callmanager to CME using two Gatekeepers and H323 Proxy.
Posted: June 11, 2006 by sankar in GatekeeperComing soon……..
Proxy registration
1. CallSignalAddress: It uses the IP address configured under the Proxy interface as the CallSignalAddress
2. RASSignalAddress: It uses the source IP address of the IP packet that contained the RAS request. It would be the IP address of the interface through which the packet was send to the gatekeeper. This is not dependent on the "h323-gateway voip interface". If you are doing registration blocking using zone subnet command, make sure to include this ip address as well.
Networking ATA, Callmanager and Voice gateway with FXS (phones)
Posted: May 26, 2006 by sankar in Analog, ATA186, Gatekeeper, Gateways, IOS GatewaysSetup :
a. Callmanager 4.1 with IP phone extension 1005 (Callmanager IP 192.168.1.200)
b. ATA 186 with H323 load , 2 phones with extension 2000, 2001 (ATA IP 192.168.1.46)
c. H323 gateway with FXS ports with phone extension 3010, 3011 (Gateway IP 192.168.1.202)
d. Gatekeeper with 3 zones created (one for CM, one for gateway and one for ATA) (GK IP 192.168.1.201)
******Key things to note about GK registration*******
a. ATA register with GK as Terminal
b. H323 gateway registers with GK as Voip-GW
c. Callmanager can be registered to the GK as Voip-GW or Terminal (Trunk configuration page)
d. GK uses proxying between Terminals and Voip-GW's. So take special note to disable proxy from each zone that involes a Terminal and Voip-GW.
Configuration of ATA
a. Use E164 numbers in UID0 and UID1.
b. No need to set Login ID's if using E.164 numbers for GK registration
c. Specify the GKID field with the zone name (with out domain name)
d. Specify the GKOrProxy field with the IP address of the gatekeeper (192.168.1.201)
e. ATA cannot specify a tech prefix (as it registers as a terminal)
Configuration of GK
GateKeeper#sh gatek end
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type F
————— —– ————— —– ——— —- —
192.168.1.46 1721 192.168.1.46 1739 ATA TERM
ENDPOINT ID: 8232D55C00000001 VERSION: 2 age= 233 secs
E164-ID: 2001
192.168.1.46 1720 192.168.1.46 1719 ATA TERM
ENDPOINT ID: 82609CF000000002 VERSION: 2 age= 233 secs
E164-ID: 2000
192.168.1.200 55419 192.168.1.200 53824 CM41 VOIP-GW
ENDPOINT ID: 824FC0F400000004 VERSION: 2 age= 18 secs
H323-ID: CCM_1
192.168.1.202 1720 192.168.1.202 50439 gateway VOIP-GW
ENDPOINT ID: 8230A09400000004 VERSION: 2 age= 40 secs
H323-ID: 192.168.1.202
E164-ID: 3011
E164-ID: 3010
Total number of active registrations = 4
GateKeeper#
Gateway Configuration
interface Ethernet0/0
ip address 192.168.1.202 255.255.255.0
half-duplex
h323-gateway voip interface
h323-gateway voip id gateway ipaddr 192.168.1.201 1719
h323-gateway voip h323-id Gateway
h323-gateway voip tech-prefix 1#
dial-peer voice 1 pots
destination-pattern 3010 —– phone 1
port 1/0/0
!
dial-peer voice 2 pots
destination-pattern 3011 —– phone 2
port 1/0/1
dial-peer voice 10 voip
destination-pattern 1… —— Pattern for calls to Callmanager , No need to prepend tech prefix as 4# is default tech prefix
session target ras
dtmf-relay h245-alphanumeric
codec g711ulaw
!
dial-peer voice 10 voip
destination-pattern 2… ——- Pattern for Calls to ATA, No need for tech prefix as ATA registers to GK as terminal
session target ras
dtmf-relay h245-alphanumeric
codec g711ulaw
!
gateway
Configuration of Callmanager
a. Add a gatekeeper (with GK's ip address, 192.168.1.201)
b. Add a Trunk (Gatekeeper controlled) and specify tech prefix 4#, the gatekeeper that was previously added, Terminal type (VOIP-GW or Terminal) and zone name (CM41)
c. Set the significant digits on incoming calls to All.
d. Add a route pattern [23]XXX and route the calls through the trunk created in step 2. 2XXX is for ATA phones and 3XXX is for FXS phones
Alias static routing — this exercise helps you to configure static routing for callmanager endpoints on the gatekeeper as a e164 address. 3001,3002, 5001, 5002 are phones registered to callmanager. The following command helps in registering these endpoints as static.
alias static 10.1.21.37 1720 gkid RACK21 gateway voip ras 10.1.21.37 49707 e164 5002 e164 5001 e164 3002 e164 3001
Remember to specify callmanager as a voip gateway and not a terminal.
PSTNSw#sh gatek end
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
————— —– ————— —– ——— —- —–
10.1.21.36 1720 10.1.21.36 60812 RACK21 TERM
E164-ID: 6001
10.1.21.37 1720 10.1.21.37 49707 RACK21 VOIP-GW S
E164-ID: 5002 (static)
E164-ID: 5001 (static)
E164-ID: 3002 (static)
E164-ID: 3001 (static)
H323-ID: TrunktoGK_1
Voice Capacity Max.= Avail.= Current.= 1
Total number of active registrations = 2
All endpoints show up as static.
proxy h323 ##############global mode enables h323 gk proxy.
interface Loopback0
ip address 3.3.3.3 255.255.255.255 ########use this for proxy’s ip address. Create a loopback.
h323 interface
h323 h323-id GKProxy ############id of h323 proxy
h323 gatekeeper id BACKBONE ipaddr 172.16.221.2 ######## id and ip of gatekeeper.
h323 t120 bypass
end
SITE3-R3#
SITE3-R3#
SITE3-R3#sh proxy h323 status
H.323 Proxy Status
==================
H.323 Proxy Feature: Enabled
Proxy interface = Loopback0: UP
Proxy IP address = 3.3.3.3
Proxy IP port = 11720
Application Specific Routing: Disabled
RAS Initialization: Complete
Proxy aliases configured:
H323_ID: GKProxy
Proxy aliases assigned by Gatekeeper:
H323_ID: GKProxy
Gatekeeper multicast discovery: Disabled
Gatekeeper:
Gatekeeper ID: BACKBONE
IP address: 172.16.221.2
Gatekeeper registration succeeded
T.120 Mode: BYPASS
RTP Statistics: OFF
Number of calls in progress: 0
SITE3-R3#
SITE3-R3#sh gatek end
GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
————— —– ————— —– ——— —- —–
3.3.3.3 11720 172.16.221.2 24999 BACKBONE H323-GW ####### The endpoint type is H323-GW.
H323-ID: GKProxy ####################################### The proxy shows up as an endpoint in the GK
192.168.121.240 1720 192.168.121.240 54298 BACKBONE VOIP-GW
Total number of active registrations = 2
SITE3-R3#
BACKBONE gatekeepr should be told to use this proxy:
—————————————————
use-proxy BACKBONE remote-zone RACK21 inbound-to gateway
use-proxy BACKBONE remote-zone RACK21 outbound-from gateway
SITE3-R3#sh proxy h323 calls
Call unique key = 1
ConferenceID = [366BC14B2D6211D6804CC3372EFE2C21]
Calling endpoint call signalling address = 172.16.121.2
Calling endpoint aliases:
E164_ID: 6464214003
Call state = H245 open logical channels
Time call was initiated = 731029554 ms
To prevent a fxs from not register with gatekeeper.
dial-peer voice 1 pots
no register e164
Restricting bandwidth between zones and with in zones
a. bandwidth interzone – specifies bw between one zone A and any other zone (You can specify zone name. Zone can be local or remote zones)
b. bandwidth remote -specifies bw to all remote zones.
c. bandwidth total – interzone + intrazone
d. bandwidth session – to specify bw per session with in a zone (intrazone)
To restrict between RACK21 and BACKBONE to just 1 call:
bandwidth remote 16 (this applies to all remote zones defined) — -tRINET ADDED 32 (why)
WITH IN A ZONE THAT USES G711, USE 128 AS BANDWIDTTH
To restrict bandwidth per session inside zone RACK21:
bandwidth session zone RACk21 128
Callmanager Service Parameter – To update bandwidth automatically.
To update bandwidth automatically from callmanager for each call use service parameter – BRQ enabled – by default its false. Set it to true and restart callmanager service.
When a call is placed at g711, gatekeeper allocates 128kbps per call.
To change this behaviour use “emulate cisco h323 bandwidth” in gateway mode in
each gateway. This will set the bw to 64 kbps for g711 and 16 for g729.
SITE3-R3#sh gatek calls
Total number of active calls = 1.
GATEKEEPER CALL INFO
====================
LocalCallID Age(secs) BW
10-63087 40 16(Kbps) ####### g729 call
Endpt(s): Alias E.164Addr
src EP: 6464214003
CallSignalAddr Port RASSignalAddr Port
192.168.121.240 1720 192.168.121.240 54298
Endpt(s): Alias E.164Addr
dst EP: 4083213001
CallSignalAddr Port RASSignalAddr Port
10.1.21.37 1720 10.1.21.37 1720
Gatekeeper A
gatekeeper
zone local RACK21 cisco.com 1.1.1.1
no shut
zone remote BACKBONE 172.16.221.2
zone prefix RACK21 646*
zone prefix BACKBONE 408*
gw-type-prefix 1# default-tech
GATEKEEPER B
gatekeeper
zone local BACKBONE cisco.com 172.16.221.2
no shut
zone remote RACK21 1.1.1.1
zone prefix RACK21 646*
zone prefix BACKBONE 408*
gw-type-prefix 1# default-tech
Default port used by callmanager is random.
All h323 gateways use port 1720 to register with gatekeeper.
To force callmanager to use 1720, you have to set service parameter “Device Name of GK-controlled Trunk That Will Use Port 1720”
This service parameter should be set with the same name as given to the Trunk to the gatekeeper. (In this ex: TrunktoGK)
gatekeeper
zone local Zone21 cisco.com 1.1.1.1 ##### Defines Zone21, domain cisco.com and ip address of gatekeeper is loopback (1.1.1.1)
zone local H323GWZone21 cisco.com##### Defines H323GWZone21 domain cisco.com (no need to re-key ip address of gatekeeper
By default registration from a zone is not restricted. To disable this feature,
### disable default registration for each zone.
no zone subnet Zone21 default enable
no zone subnet H323GWZone21 default enable
#### the following command specifically enables registration from endpoints
zone subnet Zone21 10.1.21.33/32 enable
zone subnet H323GWZone21 10.1.11.240/32 enable
gw-type-prefix 2#* default-technology
### this will route any call thats come in without a techprefix to the gateway (s) registered with techprefix of 2#. (Kind of like default gateway in routing protocols).
no shutdown #######Dont forget to give this command.
CCIE Voice notes 