ImplementingGatekeepers - IP To IPGateways

CCVP Prep:
Implementing
Gatekeepers and IP-
to-IP Gateways
Bob Liggett
Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

CCVP GWGK Presentation 1
Agenda
Preparing for the GWGK Exam

Gatekeeper Foundation
Directory Gatekeepers
Gatekeeper Redundancy
IP-to-IP Gateway
Q&A

Gatekeepers
What you need to know:
Zone and Zone Prefixes
Bandwidth
Technology Prefixes
RAS Signaling
– Gatekeeper Discovery
–Registration Requests
–Admission Requests
–Resource Availability Indicator
Intra and Inter Zone Call Set-up
How to configure all this and make it work

Gatekeeper
Foundation

A gatekeeper is an H.323 entity on the network that

provides services such as address translation and network
access control for H.323 terminals, gateways, and MCUs.
Gatekeepers can also provide other services such as
bandwidth management, accounting, and centralized dial
plan resolution for scalability.
Gatekeepers are logically separated from H.323 endpoints
such as terminals and gateways.
Gatekeepers are optional but in the H.323 specification if a
gatekeeper is present, endpoints must use the services
provided.

Mandatory Functions
Address Translation – Translates H.323 IDs (such as

gwy1@domain.com) and E.164 numbers (standard telephone
numbers) to endpoint IP addresses
Admission Control – Controls endpoint admission into the

H.323 network
Bandwidth Control – Consists of managing endpoint

bandwidth requirements, not Call Admission Control
Zone Management – The gatekeeper provides zone

management for all registered endpoints in the zone

Optional Functions
Call Authorization - Can restrict access to certain terminals or

gateways and/or have time-of-day policies restrict access an
example would be using Gatekeeper Transaction Management
Protocol (GKTMP)
Call Management - Maintains active call information and uses it to
indicate busy endpoints or redirect calls, an example would be
Resource Availability Indicator (RAI)
Bandwidth Management – A method for providing Call Admission
Control by using specific gatekeeper bandwidth commands it can
reject admission when the required bandwidth is not available
Call Control Signaling - Can route call-signaling messages
between H.323 endpoints using the Gatekeeper-Routed Call
Signaling (GKRCS) model, which has H.225 RAS, H.225, H.245
and TRP streams all flow through the gatekeeper. Alternatively, it
may use Directed Call Signaling which only has H.225 RAS
messages flow through the gatekeeper and all other streams flow
directly between the endpoints

Scenario – Acme Ice Crusher Corp.
San Jose Boston
408-555-1213 978-555-1213
IP WAN
408-555-1212 978-555-1212
PSTN
714-555-1213 212-555-1213
714-555-1212 212-555-1212
Los Angeles New York

Scenario cont. – Acme Ice Crusher Corp.
GK-WEST GK-EAST
Zone SJ 10.100.100.99/24 10.200.99.99/24 Zone BOS
10.100.100.100/24 10.200.100.100/24
GW-SJ GW-BOS
408-555-1213 978-555-1213
IP WAN
408-555-1212 978-555-1212
10.100.100.101/24 10.200.100.101/24
PSTN
GW-LA GW-NY
714-555-1213 212-555-1213
714-555-1212 212-555-1212
Zone LA Zone NY

Zones and Zone Prefixes
Zone: H.323 endpoints are grouped into zones. Each zone has one gatekeeper that manages all the
endpoints in the zone.
Zone Prefixes: A zone prefix is the part of the called number that identifies the zone to which a call goes.
Zone prefixes are usually used to associate an area or country code to a configured zone.
GK-West
GW-SJ GW-LA
PSTN PSTN
408 714

Zones and Zone Prefixes cont.
Zone: H.323 endpoints are grouped into zones. Each zone has one gatekeeper that manages all the
endpoints in the zone.
Zone Prefixes: A zone prefix is the part of the called number that identifies the zone to which a call goes.
Zone prefixes are usually used to associate an area or country code to a configured zone.
GK-West
GW-SJ GW-LA
PSTN PSTN
408 714

Zone and Zone Prefix Configuration
GK-West
!
zone local SJ icecrushers.com 10.100.100.99
zone local LA icecrushers.com
zone remote BOS icecrushers.com 10.200.99.99 1719
zone remote NY icecrushers.com 10.200.99.99.1719
zone prefix SJ 408.......
zone prefix LA 714.......
zone prefix BOS 978.......
zone prefix NY 212.......
bandwidth interzone default 64
bandwidth session zone SJ 64
no shutdown

Zone and Zone Prefix Configuration cont.
GK-West
!
no shutdown

Zone and Zone Prefix Configuration
GK-West
!
no shutdown

Bandwidth
This is a method to deploy Call Admission Control in an H.323

network
The bandwidth commands are used to specify the maximum
aggregate bandwidth for H.323 traffic and verify the available
bandwidth of the destination gatekeeper, use the bandwidth
command in gatekeeper configuration mode.
There are four options available on the gatekeeper, they are:
Interzone - Total amount of bandwidth for H.323 traffic from
the zone to any other zone.
Total - Total amount of bandwidth for H.323 traffic allowed
in the zone.
Session - Maximum bandwidth allowed for a session in the
zone.
Default - Default value for all zones.

Bandwidth Configuration
GK-West
!
zone remote NY icecrushers.com 10.200.99.99 1719
no shutdown

GK-East Gatekeeper Configuration
GK-East
!
zone local BOS icecrushers.com 10.200.99.99
zone local NY icecrushers.com
zone remote SJ icecrushers.com 10.100.100.99 1719
zone remote LA icecrushers.com 10.100.100.99 1719
bandwidth interzone zone BOS 128
bandwidth zone session 128
no shutdown
!

Gateways
Requires gateway service to be activated

Requires an interface to be associated with the gateway
service, such as an Ethernet interface
Requires the gateway to be named so it can be identified in
the gatekeeper, in our example we’ll look at GW-SJ and GW-
BOS
Requires the name of the zone and the IP address of the
gatekeeper, in our examples we’ll use the GK-West and GK-
East gatekeepers and their zones and associated IP
addresses
May require options such as technology prefixes.
Requires dial peers to route calls

Gateway Configuration
GW-SJ
!
gateway
!
interface FastEthernet0/0
ip address 10.100.100.100 255.255.255.0
h323-gateway voip interface
h323-gateway voip id GK-West ipaddr 10.100.100.99 1719
h323-gateway voip h323-id GW-SJ
!

Gateway Gatekeeper Configuration cont.
GW-BOS
!
gateway
!
interface Ethernet0/0
ip address 10.200.100.100 255.255.255.0
ip pim sparse-dense-mode
h323-gateway voip id GK-East multicast priority 1
h323-gateway voip h323-id GW-BOS
!

Technology Prefixes
H.323
Terminal
H.323
Terminal
#2 #2
gw-ny2
gw-sj2
H.323
H.323 IP Video
Video gw-sj3 GK-WEST GK-EAST gw-ny3
408 212 Voice

Voice gw-sj4 gw-ny4
Technology prefixes are used to distinguish between gateways

having specific capabilities within a given zone. The technology prefix
could be used to distinguish gateways that support terminals, video
endpoints or telephony devices or systems.

Technology Prefix Configuration
GK-West
!
gatekeeper
gw-type-prefix 1#* default-technology
no shutdown
GW-SJ
!
ip address 10.100.100.100 255.255.255.0
duplex auto
speed auto
h323-gateway voip tech-prefix 1#
Technology Prefix Configurations cont.
GK-East
!
no shutdown
GW-BOS
!
ip address 10.200.100.100 255.255.255.0
duplex auto
speed auto
Technology Prefix Configuration cont.
GK-West
!
gatekeeper
arq-reject
no shutdown
GW-SJ
!
ip address 10.100.100.100 255.255.255.0
duplex auto
speed auto
Technology Prefix Configurations cont.
GK-East
!
no shutdown
GW-BOS
!
ip address 10.200.100.100 255.255.255.0
duplex auto
speed auto

Signaling Types – RAS Messages
Discovery: Location Request:
Gatekeeper Request (GRQ) Location Request (LRQ)
Gatekeeper Confirm (GCF) Location Confirm (LCF)
Gatekeeper Reject (GRJ) Location Reject (LRJ)
Registration: Admission:
Registration Request (RRQ)
Admission Request (ARQ)
Registration Confirm (RCF)
Admission Confirm (ACF)
Registration Reject (RRJ)
Admission Reject (ARJ)
Unregistration: Disengage:
Unregistration Request (URQ)
Disengage Request (DRQ)
Unregistration Confirm (UCF)
Disengage Confirm (DCF)
Unregistration Reject (URJ)
Disengage Reject (DRJ)
Resource Availability: Request in Progress:
Resource Availability Indicator (RAI)
Request in Progress (RIP)
Resource Availability Confirm (RAC)
Status Queries:
Bandwidth Change: Info Request (IRQ)
Bandwidth Change Request (BRQ)
Info Request Response (IRR)
Bandwidth Change Confirm (BCF)
Info Request Ack (IACK)
Bandwidth Change Reject (BRJ)
Info Request Nak (INAK)

RAS Signaling – Gatekeeper Discovery
Gatekeeper Discovery (GRQ)
Gatekeeper discovery:
Uses either:
GK
GK -- SJ
SJ Unicast discovery
GRQ GRQ Multicast discovery
Allows rediscovery if gateway
decides that the gatekeeper
GCF GRJ has gone offline or sends a
GRJ message
Cisco CallManager does not
GW-SJ GW-LA send GRQs

Gatekeeper Request
h323chan_dgram_send:Sent UDP msg. Bytes sent: 71 to 10.100.100.99:1719
4d16h: RASLib::GW_RASSendGRQ: GRQ (seq# 1) sent to 10.100.100.99
4d16h: RecvUDP_IPSockData successfully rcvd message of length 62 from
10.100.100.100:49579
4d16h: GRQ (seq# 8264) rcvd
4d16h: IPSOCK_RAS_sendto: msg length 33 from 10.100.100.99:1719 to
10.100.100.100: 49579
4d16h: RASLib::RASSendGCF: GCF (seq# 8264) sent to 10.100.100.100
4d16h: GCF (seq# 1) rcvd from h323chan_dgram_send:Sent UDP msg. Bytes sent:
96 to 10.100.100.99:1719

RAS Signaling – Gatekeeper Registration
Registration Request (RRQ)
Registered Endpoints:
4085551212 = GW-SJ (Gateway)
H323VC1 = H323VC1 (Terminal)
GK
GK -WEST
-WEST 4085551214 = H323VC1 (Terminal)
RRQ
RRQ
RCF RCF • Registration is:

GW-SJ
The process by which
H323 VC1
gateways, terminals, and
MCUs join a zone and
inform the gatekeeper of
408-555-1214 their IP and alias addresses
408-555-1212
First RRQ is a “Full Registration”

Subsequent RRQs are “Lightweight”

Registration Request Example
GK-West#show gatekeeper endpoint

GATEKEEPER ENDPOINT REGISTRATION
================================
CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags
--------------- ----- --------------- ----- --------- ---- -----
10.100.100.100 1720 10.100.100.100 56937 SJ VOIP-GW
E164-ID: 4085551212
H323-ID: GW-SJ
Voice Capacity Max.= Avail.= Current.= 0
10.100.100.101 1720 10.100.100.101 49521 SJ VOIP-GW
E164-ID: 4085551213
H323-ID: GW-SJ2
Voice Capacity Max.= Avail.= Current.= 0
Total number of active registrations = 2

Registration Request (RRQ) cont.
4d16h: RASLib::GW_RASSendRRQ: RRQ (seq# 2) sent to 10.100.100.99
4d16h: RecvUDP_IPSockData successfully rcvd message of length 87 from
10.100.100.100:49579
4d16h: RRQ (seq# 8265) rcvd
10.100.100.100: 49579
4d16h: RASLib::RASSendRCF: RCF (seq# 8265) sent to 10.100.100.100
4d16h: h323chan_dgram_recvdata:rcvd from [10.100.100.99:1719] on sock[1]
4d16h: RCF (seq# 2) rcvd
4d16h: %CCH323-6-REGSTR: Gateway GW-SJ2 registered with Gatekeeper GK-West
10.100.100.100: 49579
4d16h: RASLib::RASSendIRQ: IRQ (seq# 5) sent to 10.100.100.100
4d16h: h323chan_dgram_recvdata:rcvd from [10.100.100.99:1719] on sock[1]
4d16h: IRQ rcvd

RAS Signaling – Admission Request
Admission Request (ARQ)
Dial Plan:
4085551212 : GW-SJ
GK-WEST
GK-WEST 7145551212 : GW-LA
H.225 RAS
ARQ ARQ
ACF ACF
GW-SJ GW-LA
4085551212 7145551212
Ext. 408-555-1212 calls Ext. 714-555-1212

Admission Request (ARQ) cont.
GK-West#
4d16h: RecvUDP_IPSockData successfully rcvd message of length
134 from 10.100.100.100:49579
4d16h: ARQ (seq# 8204) rcvdparse_arq_nonstd: ARQ Nonstd decode
succeeded, remlen = 1640003356
4d16h: IPSOCK_RAS_sendto: msg length 102 from
10.100.100.99:1719 to 10.200.99.99: 1719
4d16h: RASLib::RASSendLRQ: LRQ (seq# 2058) sent to 10.200.99.99
4d16h: IPSOCK_RAS_sendto: msg length 7 from 10.100.100.99:1719
to 10.100.100.100: 49579
4d16h: RASLib::RASSendRIP: RIP (seq# 8204) sent to 10.100.100.100
4d16h: RecvUDP_IPSockData successfully rcvd message of length
123 from 10.200.99.99:1719
4d16h: LCF (seq# 2058) rcvdparse_lcf_nonstd: LCF Nonstd decode
succeeded, remlen = 1640003356
4d16h: IPSOCK_RAS_sendto: msg length 69 from
10.100.100.99:1719 to 10.100.100.100: 49579
4d16h: RASLib::RASSendACF: ACF (seq# 8204) sent to 10.100.100.100

RAS Signaling - Resource Availability Indicator
(RAI)
100 %
high
GW sends RAI
„unavailable“ RAI
low GK
GK
GW sends RAI RAQ
„available“ GW
0%
A gateway informs the gatekeeper when it is running short on

resources:
This occurs when resource usage exceeds a “high water” mark.
DS0s, DSPs, CPU usage and Memory are included in calculation
A gateway that was earlier “overloaded” sends another RAI to the
gatekeeper when resources fall below a configured “low water”
mark

RAS Signaling – Inter-Zone Call Setup
RAS Signaling Sequence
GK-WEST GK-EAST
3
4
2 8
5 9
1 6 11
7
Phone A GW-SJ GW-BOS Phone B
10
408-555-1212 978-555-1212
12
1 = Phone A dials Phone B (978-555-1212) 7 = GW-BOS returns a call proceeding to GW-SJ

2 = GW-SJ sends ARQ to GK-WEST 8 = GW-BOS sends ARQ to GK-EAST
3 = GK-WEST sends LRQ to GK-EAST 9 = GK-EAST returns ACF to GW-BOS
4 = GK-EAST send LCF to GK-WEST 10 = H.245 Capability Exchange & Open Logical Channels
5 = GK-WEST returns ACF to GW-SJ 11 = GW-BOS sets up POTS call to Phone B (978-555-1212)
6 = GW-SJ sends call setup to GW-BOS 12 = Dual RTP streams between gateways

Intra-zone Calling
GK-WEST
10.100.100.99/24
Zone SJ
10.100.100.100/24
GW-SJ
408-555-1212
IP WAN
10.100.100.101/24
PSTN
GW-SJ2
408-555-1213

GW-SJ2 Configuration
GW-SJ2#
!
ip address 10.100.100.101 255.255.255.0
half-duplex
h323-gateway voip h323-id GW-SJ2
!

RAS Signaling – Intra-Zone Call Setup
RAS Signaling Sequence
GK-WEST
2 6
3 7
1 4 9
5
GW-SJ 8 GW-SJ 2 Phone B
Phone A
10 415-555-1213
408-555-1212
11
1= Phone A dials Phone B 7 = ACF

2 = ARQ 8 = H.245 Negotiations occur, Open logical channels
3 = ACF 9 = Call Extended to Phone
4 = H225 Call Setup 10 = GWB sends to GWA Call Connect
5 = H225 Call Proceeding 11 = Dual RTP Streams flow
6 = ARQ

Reference Material
Cisco IP Telephony SRND for Cisco CallManager 5.0 -
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implement
ation_design_guide_book09186a00806492bb.html
Configuring H.323 Gatekeepers
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/vvf
ax_c/callc_c/h323_c/323confg/5gkconf.htm
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/vvf
ax_c/callc_c/h323_c/323confg/4gwconf.htm#wp1124639
Understanding H.323 Gatekeepers
http://www.cisco.com/warp/public/788/voip/gk-call-routing.pdf
http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a00800
c5e0d.shtml#rasbandwidthcon
Designing a Scaleable Dial Plan
http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/voipsol/dp3_isd.ht
m
Understanding Cisco IOS Gatekeeper Call Routing
http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a00800
a8928.shtml

Directory
Gatekeepers

Hierarchical Gatekeepers
1. Small Network—Gateways Only 2. Small Network—Simplified with a Gatekeeper
3. Medium Network—Multiple Gatekeepers 4. Medium-Large Network—Multiple

Gatekeepers and a Directory Gatekeeper
Gateway Gatekeeper Directory Gatekeeper

Directory Gatekeeper
DGK
10.200.99.100/24
Zone SJ GK-WEST
Zone BOS
GK-EAST
10.100.100.100/24 10.200.100.100/24
10.100.100.99/24 10.200.99.99/24
GW-SJ GW-BOS
408-555-1213 978-555-1213
IP WAN
408-555-1212 978-555-1212
10.100.100.101/24 10.200.100.101/24
PSTN
GW-LA GW-NY
714-555-1213 212-555-1213
714-555-1212 212-555-1212
Zone LA Zone NY
Directory Gatekeeper Operation - Sequential
Sequential Operation – This is the default function and
will send an LRQ to each downstream gatekeeper in
sequence
3
LR Q 2
LRQ
Q 4 LR
LRQ 5 LRQ 1
6
Q LR
7
LR Q
LRQ
8

Directory Gatekeeper Operation - Blast
Blast Operation sends LRQs to all downstream
gatekeepers at the same time
LRQ
LR Q
Q LR
LRQ LRQ
Q LR
LR LRQ Q

Directory Gatekeeper Configuration
DGK#
!
gatekeeper
zone local DGK icecrushers.com 10.200.99.100
zone remote GK-East icecrushers.com 10.200.99.99 1719
zone remote GK-West icecrushers.com 10.100.100.99 1719
zone prefix GK-East 212.......
zone prefix GK-West 408.......
zone prefix GK-West 714.......
zone prefix GK-East 978.......
zone prefix DGK*
lrq forward-queries
lrq lrj immediate-advance
no shutdown

GK-East and GK-West Configurations
GK-East#
!
gatekeeper
zone local GK-East icecrushers.com 10.200.100.99
zone remote DGK icecrushers.com 10.200.100.102 1719
zone prefix DGK *
no shutdown

GK-East and GK-West Configurations cont.
GK-West#
!
gatekeeper
zone local GK-West icecrushers.com 10.100.100.99
zone remote DGK icecrushers.com 10.200.100.102 1719
zone prefix SJ 408…….
zone prefix LA 714…….
zone prefix DGK *
no shutdown

Resources
Gateway Configuration
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_a
dministration_guide_chapter09186a00801f00ed.html#wp1183281
Cisco IP Telephony Solution Reference Network Design
(SRND) for Cisco CallManager 5.0
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_i
mplementation_design_guide_book09186a00806492bb.html
Cisco IOS Software Library 12.3 T H.323 Gateway
Configuration
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/12
3cgcr/vvfax_c/callc_c/h323_c/323confg/index.htm

Gatekeeper
Redundancy

Gatekeeper Redundancy - HSRP
Gatekeeper configurations must be identical
Both routers must be on the same LAN subnet
HSRP multicast update timers can be configured
One Active Gatekeeper, one standby Gatekeeper, no load balancing
Switching to standby, endpoints reregister
Call state is not maintained upon failover
HSRP HSRP
GK GK GK GK
10.1.1.252 10.1.1.253 10.1.1.252 10.1.1.253
GK GK
10.1.1.254 10.1.1.254
RAS RAS
Virtual Address

Gatekeeper Redundancy – Alternate
Gatekeepers
• With H.323 alternate gatekeepers:
Are statically configured on the endpoint
Lightweight RRQs are sent from gateway to
gatekeeper as keepalives.
The endpoints detect the failure
Failover can take up to 90 seconds.
One primary and one or more alternate gatekeepers
are used with no load balancing
GK ALTGK
RAS
USGW1

Cisco Gatekeeper Redundancy: Clustering
Gatekeeper Cluster
Characteristics: Cisco Gatekeeper Update Protocol “GUP”
Endpoints point to their
primary gatekeeper Element 1
Gateways are notified of the Element 2 Element 3
GK
alternate gatekeepers during
registration GK GK
Up to 3,000 endpoints per

gatekeeper
Maximum of 7,500 GK GK
endpoints in a cluster Element 4 Element 5
Maximum of five gatekeeper
“Elements” in a cluster
Gatekeeper elements may be H.225_Trunk
in different subnets
Load Balancing is supported

Gatekeeper Clusters - Acme Ice Crusher Corp.
GK-WEST GK-EAST
Zone SJ 10.100.100.99/24 10.200.99.99/24 Zone BOS
10.100.100.100/24 10.200.100.100/24
Cluster ACME
GW-SJ GW-BOS
408-555-1213 978-555-1213
IP WAN
408-555-1212 978-555-1212
10.100.100.101/24 10.200.100.101/24
PSTN
GW-LA GW-NY
714-555-1213 212-555-1213
714-555-1212 212-555-1212
Zone LA Zone NY

Configuring Gatekeeper Clustering
GK-West
!
gatekeeper
zone cluster remote ACME icecrushers.com 10.200.99.99 1719
element GK-East 10.200.99.99 1719
zone prefix BOS 978…….
zone prefix NY 212…….
bandwidth interzone zone SJ 64
bandwidth session zone LA 128
no shutdown

Configuring Gatekeeper Clusters cont.
GK-East
!
gatekeeper
zone cluster remote ACME icecrushers.com 10.100.100.99 1719
element GK-West 10.100.100.99 1719
no shutdown

Resources
Cisco IP Telephony Solution Reference Network Design

(SRND) for Cisco CallManager 5.0
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implement
ation_design_guide_book09186a00806492bb.html
Configuring H.323 Gatekeepers and Proxies
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_
configuration_guide_chapter09186a00802b460c.html#wp1223956
Troubleshooting GUP, Alternate Endpoint and Load Balancing
http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note091
86a00800c5f06.shtml

IP-to-IP Gateway

Topologies
408 Zone 919 Zone
VZGK
GK-West GK
323-323
GW
GW-SJ IPIPGW

Features / Functions
Features
Protocol Interworking
Address Hiding, Security
NAT Traversal
Media Interworking
QoS
Call Admission Control
Billing
Lawful Intercept

Internet Calling for Audio/Video Telephony
Acme Icecrushers.com Service Provider
GK
CCM Cluster
A
Stateful FW SBC
VoIP Aware IP
PSTN
GK
SBC Signaling
Customer
RTP
Premise

Network and Address Hiding
SIP UA A IP-to-IP Gateway SIP UA B
10.1.1.1 170.1.1.1 20.1.1.1
Src 10.1.1.1:1025
Dst 170.1.1.1: SBC’s port
Src 170.1.1.1:1030
c = 10.1.1.1 Dst 20.1.1.1:5060
c = 170.1.1.1
Invite B @ 170.1.1.1 m = 20000, 20001
Invite B @ 20.1.1.1
Acts like a Back-to-Back User Agent – it would reformulate a

request with entirely new From, Via, Contact, Call-ID, and Session
Descriptor Protocol (SDP) media information.
Also for H.323 to H.323 and H.323 to SIP, the endpoints only see
the IP Address of the IP-to-IP Gateway.

CallManager
Protocol Support CallManager
Cluster Cluster
A
IP-to-IP Gateway A
(H.323-H.323)
H323 H323
SBC
CallManager
Cluster
A IP-to-IP Gateway
(H.323-SIP)
H.323 SIP
SBC
SIP IP-to-IP Gateway

(B2BUA)
SIP
SBC
SIP

Protocol Support - H323-H323 Features
CallManager A IP-to-IP Gateway A
CallManager
(H.323-H.323)
Cluster Cluster
H323 H323
SBC
• Network/Topology Hiding for Voice and • Signaling Interworking - Fast Start –

Video Calls Slow Start
• Protocol Compliance - H.323v2/v4 • Supplementary Services
• Voice Codecs • Transcoding – G711 < > G.729
G.711u,G.711a,G.723,G.726,G.729,G.728, • Transport Mode - TCP, UDP (with GK)
GSMFR, GSMEFR, Codec Transparent • Number Translation
• Video Codecs – H.261,H.263,H.264 • Quality of Service - IP Precedence ,
• Codec Filtering DSCP Marking
• Media • Call Admission Control
Media Flow Through and Media Flow Max-Connections, RSVP, IP Circuit
Around • Accounting - Call Detail Records
• DTMF • TCL IVR Support
H.245 Alphanumeric, H.245 Signal,H323 • Rotary Support - Same Codec,
RFC2833 Different Codecs
• Fax/Modem
T.38 Fax, Cisco Fax Relay, Fax Pass
Through, Modem Pass-Through
Protocol Support - H323-SIP Features
CallManager IP-to-IP Gateway
A
SIP Proxy
Cluster (H.323-SIP)
H.323 SIP
SBC
• Network/Topology Hiding for • Signaling Interworking

Voice Calls Fast Start < >Early Media
• Protocol Compliance Slow Start - >Delayed Media
H.323v2/v4 • Media - Media Flow through
RFC 3261 Signaling Compliant • Transcoding – G711 < > G.729
DNS A & SRV (RFC 2052/2782) • Transport Mode - TCP, UDP
SDP, RTP/RTCP • Quality of Service - IP Precedence , DSCP
• Voice Codecs Marking
G.711u,G.711a,G.723,G.726(16 & • Call Admission Control
24 kbps), G.729,G.728 Max-Connections, RSVP
• Codec Filtering • Accounting - Call Detail Records
• DTMF • TCL IVR Support
H.245 alpha/Signal - • VoiceXML Support for H323-SIP
RFC2833/SIPNotify
H323 RFC2833 – SIP RFC2833
• Fax/Modem
T.38 Fax, Cisco Fax Relay,
Protocol Support - SIP-SIP Features - 12.4(4)T
SIP Proxy
SIP IP-to-IP Gateway
(B2BUA)
SIP
SBC
SIP
• Network/Topology Hiding for Voice • Signaling Interworking

Calls Early Media – Early Media
• Protocol Compliance • Media
RFC 3261 Signaling Compliant Media Flow through
DNS A & SRV (RFC 2052/2782) • Transport Mode - TCP, UDP
SDP, RTP/RTCP • Quality of Service
• Voice Codecs IP Precedence , DSCP Marking
G.711u,G.711a,.726(16,24,32kbps), • Call Admission Control
G.729,G.728, G.723,G Max-Connections, RSVP
• DTMF • Rotary Support - Same Codec
RFC 2833 – RFC 2833 • Accounting
SIP Notify – SIP Notify Call Detail Records
• Fax/Modem • TCL IVR - RFC2833
T.38 Fax, Fax Passthru
Signaling
Generates two IP call legs
Media Flow-Through
Signaling Leg: 1 Signaling Leg: 2

Media Leg: 1 Media Leg: 2
SBC
Media Flow-Around
Signaling Leg: 1 Signaling Leg: 2

SBC
Media Bypasses the IP-to-IP Gateway

Via Zone Overview
Via-zone is a Cisco term for a zone that contains IP-

to-IP gateways and via-zone-enabled gatekeepers.
The via-zone-enabled gatekeeper is capable of
recognizing via-zones and sending traffic to via-
zone gateways.
Via-zones are usually located on the edge of an
Enterprise or ITSP network, and are like a VoIP
transfer point, or tandem zone, where traffic passes
through on the way to the remote zone destination.

IP-to-IP Gateway Signaling
BOBTEL.com
icecrushers.com
“via” Zone
408 Zone 919 Zone
3, 4 10, 11
VZGK
GK-West GK 919
7, 8, 9, 12
2, 5 6 14, 15
13
1 323-323
GW 919
GW-SJ IPIPGW

IP-to-IP Gateway Signaling cont.
1. A call is placed from the CallManager cluster to someone in area code 919.
2. GW-SJ sends an ARQ with the called number having the 919 area code to GK-West.
3. GK-SJ resolves 919 belonging to the via-zone gatekeeper and sends an LRQ to VZGK.
4. VZGK receives LRQ for 919 and resolves the 919 prefix to the IPIPGW.
VZGK sends FLCF to GK-West.
5. GK-West returns an ACF specifying IPIPGW to GW-SJ.
6. GW-SJ sends a SETUP message to IPIPGW for the 919 number.
7. IPIPGW sends an ARQ to VZGK with the answerCall=true parameter to admit the
incoming call.
8. VZGK responds with an ACF to admit the call. From the perspective of
VZGK the first call leg is established.
9. IPIPGW has a dial peer specifying that RAS messages should be sent to
VZGK for all prefixes. IPIPGW initiates the resending of the call by sending the ARQ
message with the answerCall=false to VZGK for 919.
10. VZGK knows that prefix 919 belongs to GK919, and since the source zone is the via-
zone, the VZGK sends an LRQ to GK919.
11. GK919 sees prefix 919 as a local zone and sends an LCF pointing to GW919.
12. VZGK returns an ACF to the IPIPGW specifying GW919.
13. IPIPGW sends a SETUP message to GW919 for the 919 call.
14. GW919 sends an ARQ to GK919 to request admission for the call.
15. GK919 sends an ACF with the answerCall=true parameter.
Acme Ice Crusher Corp. with IP-to-IP Gateway
Zone SJ Zone BOS
GK-SJ GK-BOS
GW-OS
SBC SBC
A IP WAN A
PSTN GK-NY
GK-LA
SBC
SBC
A A
Zone LA Zone NY

Acme Ice Crusher Corp. with VIA Zone
VIA Zone
ITSP
Zone SJ GK-WEST GK-EAST Zone BOS
GK-VZ
SBC
GW-SJ
GW-BOS
IP WAN
PSTN
GW-LA GW-NY
Zone LA Zone NY

Configuration
GK-West
!
gatekeeper
zone local GK408 icecrushers.com 10.100.100.99
zone remote VIA icecrushers.com 10.201.100.99 1719
zone prefix VIA *
no shutdown
IP-to-IP Gateway Configuration cont.
GW-SJ
!
ip address 10.100.100.100 255.255.255.0
half-duplex
!
gateway

GK-East
!
gatekeeper
zone remote VIA icecrushers.com 10.201.100.99 1719
zone VIA *
no shutdown
!

GW-BOS
!
ip address 10.200.100.100 255.255.255.0
duplex auto
speed auto
!
gateway

GK-VIA
!
gatekeeper
zone local GKVIA icecrushers.com 10.201.100.99
zone remote GKITSP BOBTEL.com 10.10.10.46 1719 invia GKVIA
outvia GKVIA
zone prefix GKITSP *
no shutdown
!

IPIPGW
!
voice service voip
no allow-connections any to pots
no allow-connections pots to any
allow-connections h323 to h323
h323
ip circuit max-calls 1000
ip circuit default only
!
ip address 10.16.8.145 255.255.255.0
ip route-cache same-interface
duplex auto
speed auto
h323-gateway voip id GKVIA ipaddr 10.201.100.99 1718
h323-gateway voip h323-id IPIPGW
!

Resources
Cisco Multiservice IP-to-IP Gateway

http://www.cisco.com/en/US/products/sw/voicesw/ps5640/products_configura
tion_guide_book09186a0080409b6d.html
Remote to Local Network with the Cisco Multiservice IP-to-IP
Gateway Feature
http://www.cisco.com/en/US/tech/tk1077/technologies_configuration_example
09186a0080203edc.shtml
Remote to Remote Network with the Cisco Multiservice IP-to-
IP Gateway Feature
09186a0080203edd.shtml
Remote to Remote Network with Two Cisco Multiservice IP-to-
IP Gateways
09186a0080203edb.shtml


ImplementingGatekeepers - IP To IPGateways

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ImplementingGatekeepers - IP To IPGateways

Uploaded by

Copyright:

Available Formats

CCVP Prep:

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

 Preparing for the GWGK Exam

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

A gatekeeper is an H.323 entity on the network that

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

 Address Translation – Translates H.323 IDs (such as

 Admission Control – Controls endpoint admission into the

 Bandwidth Control – Consists of managing endpoint

 Zone Management – The gatekeeper provides zone

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

 Call Authorization - Can restrict access to certain terminals or

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

San Jose Boston

Los Angeles New York

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

 This is a method to deploy Call Admission Control in an H.323

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

 Requires gateway service to be activated

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

408 212 Voice

Technology prefixes are used to distinguish between gateways

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

RCF RCF • Registration is:

First RRQ is a “Full Registration”

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

GK-West#show gatekeeper endpoint

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Ext. 408-555-1212 calls Ext. 714-555-1212

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

 A gateway informs the gatekeeper when it is running short on

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

1 = Phone A dials Phone B (978-555-1212) 7 = GW-BOS returns a call proceeding to GW-SJ

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

1= Phone A dials Phone B 7 = ACF

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

3. Medium Network—Multiple Gatekeepers 4. Medium-Large Network—Multiple

Gateway Gatekeeper Directory Gatekeeper

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved.

Preparing for the GWGK Exam

Address Translation – Translates H.323 IDs (such as

Admission Control – Controls endpoint admission into the

Bandwidth Control – Consists of managing endpoint

Zone Management – The gatekeeper provides zone

Call Authorization - Can restrict access to certain terminals or

This is a method to deploy Call Admission Control in an H.323

Requires gateway service to be activated

A gateway informs the gatekeeper when it is running short on

Cisco IP Telephony Solution Reference Network Design

Acts like a Back-to-Back User Agent – it would reformulate a

Via-zone is a Cisco term for a zone that contains IP-

Cisco Multiservice IP-to-IP Gateway