Configuring Cisco UBEs and Via-Zone Gatekeepers
Figure 9-18 shows a sample book acclimated to configure a Cisco UBE router and a viazone
gatekeeper. A attendant is configured with two accepted bounded zones: San Jose
(SJC) and Chicago (CHI). The Cisco Unified Communications Manager Express Router1
is registered in the SJC zone, and the Cisco Unified Communications Manager Express
Router3 is registered in CHI zone. Calls amid Chicago and San Jose should be routed
by the gatekeeper. Instead of acquisition calls anon amid the two zones, the gatekeeper
should avenue the calls through the VIA, which includes a Cisco UBE router.
Note The Cisco UBE action and the attendant action are performed by the same
router.
Configure the Gatekeeper
You can complete these accomplish to configure a gatekeeper:
Step 1. Create a loopback interface to use for the gatekeeper.
Step 2. Create local, remote, and VIA zones.
Two bounded zones, SJC and CHI, are configured, but instead of configuring a
standard bounded zone, the invia and outvia options are acclimated to avenue calls to
and from the zones application the VIA zone.
In accession to the SJC and CHI bounded zones, addition bounded via-zone is configured.
This area will accommodate the Cisco UBE router.
Figure 9-18 Cisco UBEs and Via-Zone Gatekeepers Agreement Topology
Step 3. Specify area and technology prefixes.
Standard area prefix acquisition is set up, and the absence technology 1# is configured.
Example 9-7 illustrates a sample via-gatekeeper configuration.
Example 9-7 Via-Zone Attendant Configuration
Chapter 9: Establishing a Connection with an Internet Telephony Account Provider 545
Router1
H.323 ID SJC-GW
Technology Prefix 1#
CUBE
H.323 ID IPIPGW
Technology Prefix 1#
Router3
H.323 ID CHI-GW
Technology Prefix 1#
Zone CHI
Via-Zone: VIA
Zone Prefix: 3...
Zone SJC
Via-Zone: VIA
Zone Prefix: 1...
Zone VIA
GK
V
Gatekeeper and
CUBE on Aforementioned Router
GK=Gatekeeper
GW=Gateway
GK(config)#interface Loopback0
GK(config-if)#ip abode 192.168.66.14 255.255.255.0
GK(config-if)#exit
GK(config)#gatekeeper
GK(config-gk)#zone bounded SJC cisco.com 192.168.66.14 invia VIA outvia VIA
GK(config-gk)#zone bounded CHI cisco.com invia VIA outvia VIA
GK(config-gk)#zone bounded VIA cisco.com
GK(config-gk)#zone prefix SJC 1*
GK(config-gk)#zone prefix CHI 3*
GK(config-gk)#gw-type-prefix 1#* default-technology
GK(config-gk)#no shutdown
Configure the Cisco UBE
After the attendant agreement is done, the Cisco UBE agreement is performed on
the aforementioned router.
You can complete these accomplish to configure the Cisco UBE feature:
Step 1. Enable H.323 interworking.
Step 2. Create a loopback interface to use as the antecedent interface for Cisco UBE to
register with the gatekeeper.
The Loopback1 interface is acclimated as the H.323 aperture interface. The Cisco
UBE router will annals in area VIA with the H.323 ID CUBE and the technology
prefix 1#.
Step 3. Create two punch peers—one pointing to San Jose and the added to Chicago.
Step 4. Enable the aperture process.
Example 9-8 illustrates a sample Cisco UBE configuration.
Example 9-8 Cisco UBE Configuration
546 Authorized Self-Study Guide: Cisco Articulation over IP (CVOICE)
GK(config)#voice account voip
GK(config-voice-service)#allow-connections h323 to h323
GK(config-voice-service)#exit
GK(config)#interface loopback1
GK(config-if)#ip abode 192.168.66.15 255.255.255.0
GK(config-if)#h323-gateway voip interface
GK(config-if)#h323-gateway voip id VIA ipaddr 192.168.66.14 1719
GK(config-if)#h323-gateway voip h323-id IPIPGW
GK(config-if)#h323-gateway voip tech-prefix 1#
GK(config-if)#exit
GK(config)#dial-peer articulation 10 voip
GK(config-dial-peer)#destination-pattern 1...
GK(config-dial-peer)#session ambition ras
GK(config-dial-peer)#exit
GK(config)#dial-peer articulation 30 voip
GK(config-dial-peer)#destination-pattern 3...
GK(config-dial-peer)#session ambition ras
GK(config-dial-peer)#exit
GK(config)#gateway