Voice Deep Dive Workbook Version 3.5 Module 8

Copyright © 2011 Internetwork Expert www.INE.com - 1 -

Expert H.323 Gatekeeper :: Tasks

Lab Instructions:

Prior to starting this lab, ensure that you have both read through the Voice Rack Rental Guide before beginning this lab, so that you are fully aware of how all equipment works and is accessed, and that you have loaded both the initial router/switch configs from INE’s members’ site, and that you have manually loaded the CUCM initial configs as described below.

Note

- Most Deep Dive lab scenarios require existing configuration before they can begin to be configured. Also, most lab scenarios use different pre-configuration from other Deep Dive labs. Therefore it is necessary to load the "Startup Configs" prior to beginning any of these lab scenarios.

- To load your router and switch configs, first log into your INE.com Members account, then navigate to the "Rack Rental" tab, and click on "Control Panel" >> "Click here to choose a configuration to be loaded on your Voice Rack", then choose the appropriately named selection for this module. This will only load your router and switch configs (pstn, r1, r2, r3, sw1, sw2).

- To load your CUCM server initial configs, please log into the CUCM Admin WebUI, and use the “Bulk Administration” tool to upload & import the appropriately named “DD-ModXX-CUCM-Startup.tar" file that was included in your Members account for this module. Here are two brief demonstration videos on how to successfully accomplish this upload and import into CUCM: Importing or Exporting Configurations in CSV file from CUCM (15 mins), and Fixing Any Issues That May Arise With Importing CSS and CdPTP & CngPTPs (8 mins).

Voice Deep Dive Workbook Version 3.5 Module 8

Copyright © 2011 Internetwork Expert www.INE.com - 2 -

8.1 IOS H.323 Gatekeeper

Provision the CorpHQ router (R1) as an H.323 Gatekeeper using the following specifications:

o Use the Loopback0 as the source of all Gatekeeper RAS traffic

o Create two zones, call one "SEA" and the other called "AMS", both with the domain name of "ine.com"

8.2 CUCM Gatekeeper with Security

Register both CUCM servers to the "SEA" H.323 Gatekeeper using the following specifications:

o You are not permitted to enter the zone name anywhere in the CUCM

o Use the best H.323 Trunk type for the job

o Register them as gateways using the H.323 ID Prefix of "SEA-CUCM-GW"

o Register both using the dynamic technology prefix of 115#

8.3 CUCME Gatekeeper with Security

Register the already-provisioned CUCME running on Branch2 router (R3) to the "AMS" H.323 Gatekeeper using the following specifications:

o Register the gateway using the IP address of the existing CME Source Address (Voice VLAN for Branch2 IP Phones)

o Register it using the H.323 ID of "AMS-CME-GW"

o Register it using the dynamic technology prefix of 225#

o First allow local CME DN's to register with the GK just to see what they look like on the GK (run a "show gatekeeper endpoint" on GK to see), but then remove them and ensure that do not show up when the "show gatekeeper endpoint" command is run on R1-GK

8.4 CUCM Calls via Gatekeeper to CUCME

Configure such that you can route calls from IP Phones at the CUCM cluster (both CorpHQ and Branch1 phones) over to the CUCME, with the Gatekeeper resolving numbers to IP addresses, and keeping track of the calls

You are not permitted to use the "default" technology prefix anywhere in the Gatekeeper configuration to route the call

8.5 CUCME Calls via Gatekeeper to CUCM

Configure such that you can route calls from IP Phones at the CUCME cluster (Branch2 phones) over to the CUCM, with the Gatekeeper resolving numbers to IP addresses, and keeping track of the calls

You are not permitted to use the "default" technology prefix anywhere in the Gatekeeper configuration to route the call

Voice Deep Dive Workbook Version 3.5 Module 8

Copyright © 2011 Internetwork Expert www.INE.com - 3 -

8.6 Gatekeeper Call Admission Control

Configure the Gatekeeper (only) so that up to 25 calls can traverse between CUCM and CUCME in either direction, however only if each call is a G.729 or lesser bandwidth call

8.7 Advanced Gatekeeper Configuration

Change the registration of CUCME Gatekeeper from registering with the technology prefix of 225# to the technology prefix of 115#, and then change whatever is necessary on CUCM and/or the Gatekeeper to ensure that calls still route properly in both directions