Cvoice v60 Lab Guide

CIPT1
Cisco Voice over IP

Version 6.0
Lab Guide
Editorial, Production, and Web Services: 02.15.08
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be used in commercial training, and may not be distributed for purposes other than individual self-study.
DISCLAIMER WARRANTY: THIS CONTENT IS BEING PROVIDED AS IS. CISCO MAKES AND YOU RECEIVE NO WARRANTIES IN CONNECTION WITH THE CONTENT PROVIDED HEREUNDER, EXPRESS, IMPLIED, STATUTORY OR IN ANY OTHER PROVISION OF THIS CONTENT OR COMMUNICATION BETWEEN CISCO AND YOU. CISCO SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. This learning product may contain early release content, and while Cisco believes it to be accurate, it falls subject to the disclaimer above.
Table of Contents
Lab Guide
Overview Outline Lab Topology Job Aids Dial Plan Dial Plan Conventions PSTN Configuration Lab 2-1: Configuring Analog Voice Interfaces Activity Objective Visual Objective Required Resources Command List Task 1: Configure an Analog Voice Port Task 2: Verify Analog Port Settings Lab 2-2: Configuring POTS Dial Peers Activity Objective Visual Objective Required Resources Command List Job Aids Task 1: Configure POTS Dial Peers Lab 2-3: Configuring VoIP Dial Peers Activity Objective Visual Objective Required Resources Command List Job Aids Task 1: Configuring VoIP Dial Peers Task 2: Configure Codecs Task 3: Calculate Bandwidth Requirements Task 4: Configure Codec Negotiation Lab 2-4: Configuring Digital Voice Interfaces Activity Objective Visual Objective Required Resources Command List Job Aids Task 1: Configure the BR T1 CAS Trunk to the PSTN Task 2: Configure the HQ ISDN PRI Trunk to the PSTN Lab 3-1: Implementing H.323 Gateways Activity Objective Visual Objective Required Resources Command List Job Aids Task 1: Configure an H.323 Gateway Lab 3-2: Implementing SIP Gateways Activity Objective Visual Objective Required Resources Command List Job Aids Task 1: Configure a Gateway for SIP Lab 4-1: Implementing Numbering Plans Activity Objective Visual Objective
1
1 1 2 5 5 5 6 7 7 7 7 8 8 10 12 12 12 12 12 13 13 15 15 15 15 15 16 17 18 19 20 21 21 21 21 21 22 23 25 27 27 27 27 27 28 29 30 30 30 30 30 31 31 33 33 33
Required Resources Command List Job Aids Task 1: Configure a Numbering Plan for HQ and Branch Offices Lab 4-2: Implementing PSTN Dial Plans Activity Objective Visual Objective Required Resources Command List Job Aid Task 1: Configure Dial Peers Task 2: Configure Digit Manipulation Lab 4-3: Configuring Path Selection Activity Objective Visual Objective Required Resources Command List Job Aid Task 1: Configure Hunt Groups Task 2: Configure Redundant Calling Paths Task 3: Configure TEHO Lab 4-4: Implementing Calling Privileges Activity Objective Visual Objective Required Resources Command List Job Aid Task 1: Create COR Labels Task 2: Configure COR Lists Task 3: Configure Dial Peers to Use COR Lists Lab 5-1: Configuring Basic Gatekeeper Functionality Activity Objective Visual Objective Required Resources Command List Job Aid Task 1: Configure Local Zones Task 2: Configure Zone and Technology Prefixes Task 3: Configure Gateways to Register with a Gatekeeper Lab 5-2: Implementing Gatekeeper-Based CAC Activity Objective Visual Objective Required Resources Command List Job Aids Task 1: Calculate Bandwidth Requirements Task 2: Configure Zone Bandwidth Lab 6-1: Configuring a Cisco UBE Activity Objective Visual Objective Required Resources Command List Job Aids Task 1: Configure a Cisco UBE for Protocol Interworking and Address Hiding Answer Key Lab 2-1 Answer Key: Configuring Analog Voice Interfaces Lab 2-2 Answer Key: Configuring POTS Dial Peers Lab 2-3 Answer Key: Configuring VoIP Dial Peers Lab 2-4 Answer Key: Configuring Digital Voice Interfaces Lab 3-1 Answer Key: Implementing H.323 Gateways
ii Cisco Voice over IP (CVOICE) v6.0
33 33 35 36 37 37 37 37 37 38 39 39 41 41 41 41 41 42 42 43 44 45 45 45 45 45 46 46 47 49 50 50 50 50 51 52 52 53 53 56 56 56 56 56 57 58 58 59 59 59 59 59 60 60 61 61 62 63 64 67
2008 Cisco Systems, Inc.
Lab 3-2 Answer Key: Implementing SIP Gateways Lab 4-1 Answer Key: Implementing Numbering Plans Lab 4-2 Answer Key: Implementing PSTN Dial Plans on Cisco IOS Gateways Lab 4-3 Answer Key: Configuring Path Selection Lab 4-4 Answer Key: Implementing Calling Privileges on Cisco IOS Gateways Lab 5-1 Answer Key: Configuring Basic Gatekeeper Functionality Lab 5-2 Answer Key: Implementing Gatekeeper-Based CAC Lab 6-1 Answer Key: Configuring a Cisco UBE
68 69 70 74 76 79 81 82
Cisco Voice over IP (CVOICE) v6.0
iii
iv
CVOICE
Lab Guide
Overview
This guide presents the instructions and other information concerning the lab activities for this course. You can find the solutions in the lab activity Answer Key.
Outline
This guide includes these activities:

Lab 2-1: Configuring Analog Voice Ports Lab 2-2: Configuring POTS Dial Peers Lab 2-3: Configuring VoIP Dial Peers Lab 2-4: Configuring Digital Voice Ports Lab 3-1: Implementing H.323 Gateways Lab 3-2: Implementing SIP Gateways Lab 4-1: Implementing Numbering Plans Lab 4-2: Implementing PSTN Dial Plans on Cisco IOS Gateways Lab 4-3: Configuring Path Selection Lab 4-4: Implementing Calling Privileges on Cisco IOS Gateways Lab 5-1: Configuring Basic Gatekeeper Functionality Lab 5-2: Implementing Gatekeeper-Based CAC Lab 6-1: Configuring a Cisco UBE to connect to an ITSP Answer Key
Lab Topology
This is a diagram of the lab topology used in the labs for Cisco Voice over IP (CVOICE) v6.0.
CVOICE 6.0 Lab Topology

Phone1-1 7941/61 1101 Phone2-1 7941/61 1102
Two-Pod Group
GK1 GK2
Phone1-2 7941/61 2101 Phone2-2 7941/61 2102
IP WAN
Phone3-1 1103
HQ-1
FXS
l ria Se T1/E 1
HQ-2
FXS Phone3-2 2103 Phone4-2 2104
Phone4-1 1104
PSTN BR-1 BR-2

FXS
Phone6-1 1202
FXS
Phone6-2 2202
Phone5-2 7941/61 2201
Phone5-1 7941/61 1201
PSTN Phone-1
PSTN Phone-2
POD-1
(7941/61 or PC with NetMeeting)
POD-2
CVOICE v6.03
2008 Cisco Systems, Inc. All rights reserved.
The addressing of the classroom pods is described in the following tables.
Address Table for Odd-Numbered Classroom Pods

Device Name Abbreviation HQX Assigned Pod X Network Address 10.X.2.101 Additional Information HQX Voice VLAN HQX Data VLAN Allows Telnet to switch from PodX Used as source interface To PodY, HQY To PodX, BRX T1 PRI trunk to PSTN:

Device Name Headquarters Pod X Gateway
Interface Fa0/0.X02
Fa0/0.X03 Fa0/0.198
10.X.3.101 3.X.0.1
Loopback 0
10.X.250.101
Serial 0/0/0 Serial 0/0/1 T1 01/0
10.XY.XY.101 10.X.4.101
PRI Framing: ESF Line code: B8ZS
Pod X Switch
PodXSW
VLAN198 VLANX02 VLANX03
3.X.0.2
Management VLAN HQX voice VLAN HQX data VLAN
Branch Pod X Gateway
BRX
Fa0/0.X05 Fa0/0.X06 Fa0/0.198
10.X.5.102 10.X.6.102 3.X.0.3
BRX voice VLAN BRX data VLAN Allows Telnet to switch from PodX Used as source interface BRX voice VLAN BRX data VLAN
Loopback 0
10. X.250.102
Branch Pod X Switch
BRXSW
VLANX05 VLANX06
Gatekeeper Pod X
GKX
Fa0/0. X03 Fa0/0.198
10. X.3.102 3.X.0.4
HQX data VLAN Allows Telnet to switch from PodX

Lab Guide
Note
X = Pod number 1, 3, or 5. Y = Even number pod in pod pair.
Address Table for Even-Numbered Classroom Pods

Device Name Abbreviation HQY Assigned Pod Y Network Address 10.Y.2.101 Additional Information HQY Voice VLAN HQY Data VLAN Allows Telnet to switch from PodY Used as source interface To PodX, HQX To PodY, BRY T1 PRI trunk to PSTN: PRI Framing: ESF Line code: B8ZS Pod Y Switch PodYSW Y VLAN198 VLANY02 VLANY03 Branch Pod Y Gateway BRY Y Fa0/0.Y05 Fa0/0.Y06 Fa0/0.198 10.Y.5.102 10.Y.6.102 3.Y.0.3 3.Y.0.2 Management VLAN HQY Voice VLAN HQY Data VLAN BRY Voice VLAN BRY Data VLAN Allows Telnet to switch from PodY Used as source interface BRY Voice VLAN BRY Data VLAN 10. Y.3.102 HQY Data VLAN
Device Name Headquarters Pod Y Gateway
Interface Fa0/0.Y02
Fa0/0.Y03 Fa0/0.198
10.Y.3.101 3.Y.0.1
Loopback 0
10.Y.250.101
Serial 0/0/0 Serial 0/0/1 T1 01/0
10.XY.XY.101 10.Y.4.101
Loopback 0
10. Y.250.102
Branch Pod Y Switch
BRYSW
VLANY05 VLANY06
Gatekeeper Pod Y
GKY
Fa0/0. Y03
Note
Y = Pod number 2, 4, or 6. X = Odd number pod in pod pair.
Job Aids
These job aids are available to help you complete lab activity.
Dial Plan
The table represents the dial plan that will be used in the labs. Classroom Dial Plan
Pod Number HQX 1 1101(IP) 1102(IP) 1103(Analog) 1104(Analog) 1201(IP) 1202(Analog) 331-555-1001 2 2101(IP) 2102(IP) 2103(Analog) 2104(Analog) 2201(IP) 2202(Analog) 332-555-2001 X X101(IP) X102(IP) X103(Analog) X104(Analog) X201(IP) X202(Analog) 33X-555-X001
BRX PSTN Area code and exchange HQ BR
331-551 331-552
332-551 332-552
33X-551 33X-552
Dial Plan Conventions

As with IP addresses, the dial plan convention should allow you to anticipate the number of any telephones in the classroom. The highlights of the classroom dial plan strategy include those listed here:
The classroom will use a 10-digit dial plan to call the PSTN. Calls to the pod PSTN phones should require a 9 and then the telephone number.
The classroom will use an 11-digit dial plan to call other pod phones through the PSTN. Calls to the other pod phones require a 9 + 1 and then the telephone number.
International calls should require a 011 international code. The classroom uses four extension digits to place local calls. The first digit identifies the pod number (1 to 4). The second and third digits identify the device (PSTN = 00, HQ = 10, BR = 20). The fourth digit identifies the telephone.
Initially, a caller should be able to complete calls between same pod sites using just the extension number. Site codes will be assigned in the dial plan labs.

Lab Guide
PSTN Configuration
The HQ router will connect to the PSTN using an ISDN PRI connection while the BR router will connect to the PSTN using a T1 CAS.
HQ to PSTN
The HQ PSTN parameters are as follows:

ISDN switch type is primary-ni ISDN T1 connection Timeslots 1 to 4 ESF framing B8ZS line code
BR to PSTN
The BR PSTN parameters are as follows:
CAS incoming T1 connection: Type E&M FGD Timeslots 1 to 2 ESF framing B8ZS line code B8ZS line code
CAS outgoing T1 connection: Type FGD-EANA Timeslots 3 to 4 ESF framing B8ZS line code
Lab 2-1: Configuring Analog Voice Interfaces

Complete this lab activity to practice what you learned in the related module.
Activity Objective
In this activity, you will become familiar with existing analog voice ports. You will learn how to customize your analog ports by configuring various port parameters. After completing this activity, you will be able to meet these objectives:

Identify default voice port settings Customize and verify analog port operations
Visual Objective
The figure illustrates what you will accomplish in this activity.
Lab 2-1: Configuring Analog Voice Interfaces

Phone1-1 7941/61 1101 Phone2-1 7941/61 1102
Two-Pod Group
GK1 GK2
Phone1-2 7941/61 2101 Phone2-2 7941/61 2102
IP WAN
Phone3-1 1103
HQ-1
FXS
l ria Se T1/E 1
HQ-2
FXS Phone3-2 2103 Phone4-2 2104
Phone4-1 1104
PSTN BR-1 BR-2

FXS
Phone6-1 1202
FXS
Phone6-2 2202
Phone5-2 7941/61 2201
Phone5-1 7941/61 1201
PSTN Phone-1
PSTN Phone-2
POD-1
POD-2
CVOICE v6.04
Required Resources
These are the resources and equipment that are required to complete this activity:

Analog telephones RJ-11 cables

Lab Guide
Command List
The table describes the commands that are used in this activity. Voice Port Commands
Command Description Sets the regional analog voice interface-related tone, ring, and cadence setting. Resets the value of the parameter to its default value. Specifies the ring cadence for an FXS voice port.
cptone country-code default parameter ring cadence {patternnumber | define pulse interval} timeouts initial secs voice-port port-number show voice port portnumber (summary)
Sets the number of seconds that the system will wait for the caller to input the first digit. Enters voice-port configuration mode. Views the voice port status and settings. Displays all default settings for each port. Specify a particular voice port to view only its settings. Use the summary option to view a summary table of the voice ports.
Task 1: Configure an Analog Voice Port

In this task, you will examine analog voice ports and configure analog voice port parameters.
Activity Procedure
Complete these steps:
Step 1
On both the HQ and BR routers, connect the analog phones to the FXS ports of the voice-enabled router using RJ-11 cables. Verify that the connections are correct by lifting the handset on both telephones and listening for the dial tone. If the dial tone is not present, troubleshoot the problem. Make sure that the router is powered on and that the cable is firmly seated. If the problem persists, ask your instructor for help. Using show commands, identify the available voice ports, their type, and their default settings.
Not all settings are applicable to all types of ports; for example, ring frequency and ring cadence apply only to FXS ports.
Step 2
Step 3
Note
Step 4
Record the information here. Voice Port 1 Voice Port 2 __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ Voice Port 3 __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ Voice Port 4 __________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________
Port type Port number Phone number Operational state Echo cancellation Echo cancel coverage Initial timeout Region tone Signal type Ring frequency Ring cadence
Step 5
__________ __________ __________ __________ __________ __________ __________ __________ __________ __________ __________
Because many companies have international offices, it is important to know how to configure the voice port to match the standard signaling of a country. For this step, assume that you are configuring this router for Australia. On one FXS port that your telephone is connected to, configure the call progress tone setting for Australia using the cptone command. Notice that when you change the call progress tone setting, it automatically changes the ring cadence setting to match. Test the change by lifting the handset. You should hear a different dial tone. Verify the changes with show commands and record the new settings here. Region tone ________________________ Ring cadence _______________________ Once you have tested the tones for Australia, experiment with settings for other countries.
Step 6
What is the default initial timeout setting from Step 4? ___________ On at least one FXS port on both the HQ and BR routers, change the initial timeout value to 4 seconds. Lift the handset and listen for more than 4 seconds. Can you dial digits after the dial tone stops? Reset the initial timeout to the default. Because you will be working with two telephones at the HQ router all week, you may want one telephone to have a distinctive ring. Configure the ring cadence on one FXS port using the ring cadence pattern-X command. You will be able to test this ring cadence in the next lab. What ring cadence pattern did you specify? ____________
Step 7

Lab Guide
Activity Verification
You have completed this task when you attain this result:
You have configured and verified analog voice port parameters.
Task 2: Verify Analog Port Settings

In this task, you will verify your analog voice port operation and configuration.
Activity Procedure
Complete this step:
Step 1
Use show voice port commands to verify that your analog voice ports are up and running.
Your output should resemble this.
HQ-1# show voice port summary IN PORT CH SIG-TYPE ADMIN OPER STATUS OUT STATUS EC
========= == ============ ===== ==== ======== ======== == 0/0/0 0/0/1 --fxs-ls fxs-ls up up dorm on-hook dorm on-hook idle idle y y
HQ-1# show voice port 0/0/0 Foreign Exchange Station 0/0/0 Slot is 0, Sub-unit is 0, Port is 0 Type of VoicePort is FXS VIC2-2FXS
Operation State is DORMANT Administrative State is UP No Interface Down Failure Description is not set Noise Regeneration is enabled Non Linear Processing is enabled Non Linear Mute is disabled Non Linear Threshold is -21 dB Music On Hold Threshold is Set to -38 dBm In Gain is Set to 0 dB Out Attenuation is Set to 3 dB Echo Cancellation is enabled Echo Cancellation NLP mute is disabled Echo Cancellation NLP threshold is -21 dB Echo Cancel Coverage is set to 64 ms
10 Cisco Voice over IP (CVOICE) v6.0 2008 Cisco Systems, Inc.
Echo Cancel worst case ERL is set to 6 dB Playout-delay Mode is set to adaptive Playout-delay Nominal is set to 60 ms Playout-delay Maximum is set to 250 ms Playout-delay Minimum mode is set to default, value 40 ms Playout-delay Fax is set to 300 ms Connection Mode is normal Connection Number is not set Initial Time Out is set to 10 s Interdigit Time Out is set to 10 s Call Disconnect Time Out is set to 60 s Supervisory Disconnect Time Out is set to 750 ms Ringing Time Out is set to 180 s Wait Release Time Out is set to 30 s Companding Type is u-law Region Tone is set for US Analog Info Follows: Currently processing none Maintenance Mode Set to None (not in mtc mode) Number of signaling protocol errors are 0 Impedance is set to 600r Ohm Station name None, Station number None Translation profile (Incoming): Translation profile (Outgoing): Voice card specific Info Follows: Signal Type is loopStart Ring Frequency is 25 Hz Hook Status is On Hook Ring Active Status is inactive Ring Ground Status is inactive Tip Ground Status is inactive Digit Duration Timing is set to 100 ms InterDigit Duration Timing is set to 100 ms Hookflash-in Timing is set to max=1000 ms, min=150 ms Hookflash-out Timing is set to 400 ms No disconnect acknowledge Ring Cadence is defined by CPTone Selection Ring Cadence are [20 40] * 100 msec Ringer Equivalence Number is set to 1

Lab Guide
11
Lab 2-2: Configuring POTS Dial Peers

Activity Objective
In this activity, you will configure POTS dial peers to establish locally terminated calls and calls to the PSTN. After completing this activity, you will be able to meet these objectives:

Configure dial peers for locally terminated calls Determine the appropriate method of digit forwarding and manipulation Verify basic call setup through debug commands Use appropriate show and debug commands to monitor and troubleshoot the connections
Visual Objective
Lab 2-2: Configuring POTS Dial Peers

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone3-x X101 Phone4-x X102
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.05
Required Resources

One PSTN device (instructor-controlled) Local telephones
Command List
The table describes the commands that are used in this activity.
12
Dial Peer Commands

Command Description Displays real-time voice port module signaling; displays digits as they are received by the voice port Displays real-time call control processing and call leg information Configures a telephone number for this dial peer Enters dial-peer configuration mode Specifies which digits to forward for voice calls Configures the port for this dial peer Displays information on active calls Displays dial-peer configuration information Displays which dial peers are matched when a particular telephone number is dialed Displays summary information on active calls
debug vpm signal debug voip ccapi inout destination-pattern string dial-peer voice tag pots forward-digits port port-number show call active voice show dial-peer voice (tag)|(summary) show dialplan number number show voice call summary
Job Aids
There are no job aids for this lab activity.
Task 1: Configure POTS Dial Peers

In this task, you will configure dial peers so that you can make calls between two telephones connected to your voice-enabled router.
Activity Procedure
Step 1
Using the Classroom Dial Plan table in the Job Aids topic, verify the telephone numbers that you will use for your local telephones. Note these numbers here. HQ IP Phone 1 ____________________ HQ IP Phone 2 ____________________ HQ Analog Phone 1 ________________ HQ Analog Phone 2 __________________ BR IP Phone 1 ____________________ BR Analog Phone 1 __________________
Step 2
Configure POTS dial peers to enable calls between the locally terminated POTS telephones using their four-digit extension. Normally, you want the dial peer tag (name) to be as descriptive as possible (for example, dial-peer 1201 for extension 1201, dial-peer 911 for emergency services, and so on). Place calls in both directions to test the configuration.
Do not create dial peers 1 through 9, 97, 910, 9110, 9911, or 911 because these dial peers will be used in future labs.
Note
Step 3
Use the appropriate show commands to view your newly configured dial peers.
Lab Guide 13
Step 4
Place a call between local telephones and leave them both off hook. Use the appropriate show commands to view your active call. Find this information. How many and what type of call legs were created? ____________ Which codec is being used for this call? ____________ What is the translated calling number? ___________ called number? ___________
Step 5
Use the debug command to see digits being collected by the voice port. Once debugging is turned on, place a call between telephones to view the digit collection.
Make sure terminal monitor is turned on to view the debug output.
Note
Step 6
Verify and experiment with previously configured voice port parameters such as cptone and ring cadence. Listen to the distinctive rings you have configured. You may have to shut down and restart the voice port for the new ring cadence to take effect.
You have made calls between your locally terminated telephones in both directions.
14
Lab 2-3: Configuring VoIP Dial Peers

Activity Objective
In this activity, you will establish basic VoIP connectivity between telephones in your pod and investigate the use of appropriate VoIP dial-peer parameters. After completing this activity, you will be able to meet these objectives:

Configure basic VoIP dial peers using the default parameters to process a call Change the codec settings on VoIP dial peers and investigate how this change affects the ability to make calls Determine the required bandwidth for a voice call using G.711 or G.729 codecs and test call quality Configure codec negotiation
Visual Objective
Lab 2-3: Configuring VoIP Dial Peers

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.06
Required Resources
No new resources are required.
Command List
Lab Guide
15
VoIP Commands
Command Description Specifies which codec is to be used for calls matching this dial peer. Configures one entry in the codec list under the voice class codec command. Repeat this command as many times as you need to specify codecs in this list. Displays real-time call control processing and call leg information. Sets the specified parameter back to its default setting. For example, default codec will set the dial peer to use the default codec for that device. Enters dial-peer configuration mode and specifies VoIP. Specifies the destination IP address for the gateway terminating a VoIP call. Displays DSP usage. Displays information on active calls. Displays dial-peer configuration information. Displays which dial peers are matched when a particular telephone number is dialed. Enters voice class codec configuration mode. Applies a predefined codec list to a dial peer. The tag must match the tag of the defined codec class.
codec codec-name codec preference 1-14 codec-name debug voip ccapi inout default parameter
dial-peer voice tag voip session target ipv4:x.x.x.x show voice dsp show call active voice show dial-peer voice (tag)|(summary) show dialplan number number voice class codec tag voice-class codec tag
Job Aids
16
Task 1: Configuring VoIP Dial Peers

In this task, you will configure basic VoIP dial peers using the default parameters to process a call. You will verify configuration by placing calls across the IP network from your HQ to BR sites.
Activity Procedure
Step 1
Configure VoIP dial peers to reach the router-attached telephones connected to the equipment belonging to your pod BR and HQ routers using their extension numbers. In preparation, note the two telephone numbers for your HQ and BR here. Also note a valid IP address on the other router. HQ telephone numbers ___________________ ______________________ HQ IP address __________________________ BR telephone numbers ___________________ ______________________ BR IP address __________________________
Step 2 Step 3
Test your configuration by placing calls between the BR and HQ telephones. Configure VoIP dial peers to reach both of the router-attached telephones that are connected to the equipment belonging to your partner pod. In preparation, note the two telephone numbers for your partner here. Also note a valid IP address on the partner router. Partner HQ telephone numbers___________________ Partner HQ IP address __________________________ Partner BR telephone numbers___________________ Partner BR IP address __________________________ ______________________ ______________________
Step 4 Step 5
Test your configuration by placing calls to both of the partner telephones. Use show commands to verify the following:

Which dial peer will be matched when a specific number is dialed Active call parameters Which DSP resources are being used for the call
Step 6
Use debug commands to verify the following:

The calling number The called number Which dial peer was matched

Lab Guide
17
You have placed calls to both of the partner telephones.
Task 2: Configure Codecs

In this task, you will change the codec settings on VoIP dial peers and investigate how it affects the ability to make calls. When doing this lab, make sure that codecs are configured correctly on both sides of the connection before proceeding.
Activity Procedure
Step 1
Use show commands to verify the default codec setting and note it here. Default codec___________________
Step 2
Change the codec on the HQ VoIP dial peer pointing to BR. Set the codec to g723r53. Place a call from one site to the other. Both HQ and BR should verify that the call was successful, and if so, which codec was used. Was the call successful? ______________ Codec used _______________
Step 3 Step 4
Step 5 Step 6
Change the codec on the BR VoIP dial peer pointing to HQ to match the HQ codec. Verify whether the codec was successful, and if so, which codec was used. Was the call successful? ______________ Codec used _______________
Step 7
Change the codec setting back to default.
You have successfully configured the codec setting for VoIP calls.
18
Task 3: Calculate Bandwidth Requirements

In this task, you will determine the required bandwidth for a voice call using G.711 or G.729 codecs, and test call quality.
Activity Procedure
Step 1
Using the bandwidth requirement concepts, determine the required bandwidth for G.711 and G.729 codecs using a 20-ms sample size, without header compression on these links. G.711 PPP link ___________________________ G.711 Frame Relay link ____________________ G.729 PPP link ___________________________ G.729 Frame Relay link ____________________
Note
Frame Relay and PPP have the same overhead.
Step 2 Step 3
Change the codec on both HQ and BR to g711ulaw. Place a call from HQ to BR over the IP network. Is the quality acceptable? If not, why not? _______________________________
Step 4
Leave the first call up and place a second call from HQ to BR over the IP network. Is the quality acceptable? If not, why not? _______________________________
Step 5 Step 6
Change the codec on both ends of the connection to g729r8. Repeat Steps 3 and 4 using the G.729 codec. Has the quality improved? _______________ Why or why not? _______________________________________
Step 7
Change the codec on both HQ and BR back to the default setting. What command did you use to reset to the default? __________________________
You can explain how and when to use RTP header compression.

Lab Guide
19
Task 4: Configure Codec Negotiation

As you saw in the previous labs, configuring a specific codec at the dial-peer level restricts that dial peer to responding with only a single codec choice during negotiation. At times, it is desirable to respond with a list of codecs to match the incoming call. For example, when a call is coming from the LAN segment, it may negotiate a G.711 codec for better voice quality because there is enough bandwidth to carry it. For a call coming into the router from a WAN segment, you may want to match a codec for compressed voice. For a single dial peer to match more than one codec, you must configure a list of codecs to negotiate. In this task, you will configure codec negotiation.
Activity Procedure
Step 1
Define a codec preference list. On HQ, select g711ulaw as the first choice and g729r8 as the second choice. On BR, select g729r8 as the first choice and g711ulaw as the second choice. Apply the codec list to the VoIP dial peer pointing to the IP address of your partner. Test calls in both directions. Use show commands to determine the order of preference for codec selection. Discuss the results with your partner. Remove the codec list and its application in the dial peer. Save your configuration.
Step 2 Step 3
Step 4 Step 5
You can explain how and when to configure codec negotiation.
20
Lab 2-4: Configuring Digital Voice Interfaces

Activity Objective
In this activity, you will configure T1 CAS and PRI trunks to the PSTN on the HQ and BR gateway routers. After completing this activity, you will be able to meet these objectives:

Configure a T1 CAS interface for correct signaling, framing, and timeslot association Configure a PRI interface for correct signaling, framing, and timeslot association Configure the appropriate ports and dial peers to place calls to the PSTN
Visual Objective
Lab 2-4: Configuring Digital Voice Interfaces

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se
HQ-2
Phone3-x X101 ISDN Phone4-x X102
ISDN Phone4-1 1102 T1/E1
PSTN
T1/E1 CAS
BR-1
FXS
Phone5-1 7941/61
CAS
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.07
Required Resources
A phone at the PSTN
Command List

Lab Guide
21
T1 Interface Commands
Command Description Enters controller configuration mode Specifies which digits to forward for voice calls Selects the frame type for the E1 or T1 data line Selects the line-code type for T1 or E1 lines Resets the specified ISDN interface Sets the clocking for individual T1 or E1 links Allows the ports on a specified network module or VWIC to use the network clock for timing Specifies the DS0 time slots that make up a logical voice port on a T1 controller; also specifies the signaling type by which the router communicates and defines T1 channels for voice calls and the CAS method by which the router connects to the PBX or PSTN Defines the telephone company switch type Enters interface configuration mode Routes all incoming voice calls to the modem and determines how they will be treated Defines Layer 2 and Layer 3 user- or networkside emulation Specifies the prefix of the dialed digits for a dial peer Specifies an ISDN PRI group on a channelized T1 or E1 controller.
controller {t1 | e1} slot/subslot/port forward-digits {num-digit | all | extra} framing {sf | esf} linecode {ami | b8zs} clear interface slot/port clock source {[primary] line | internal | free-running} network-clock-participate {aim | slot | wic} slot-number ds0-group ds0-group-number timeslots <timeslot-list> type {e&m-delay-dial | e&m-fgd | e&mimmediate-start | e&m-wink-start | fxo-ground-start | fxo-loopstart | fxs-ground-start | fxsloop-start} dtmf dnis isdn switch-type {countryspecific-switch-type} interface {bri | pri} interfacenumber isdn incoming-voice voice isdn protocol-emulate {user | network} prefix <string> pri-group timeslots timeslotrange [nfas_d {backup | none | primary {nfas_int number | nfas_group number | rlm-group number}} | service] network-clock-participate {aim | slot | wic} slot-number show voice port [slot/port:ds0group | summary] show controllers t1 number [bert]
Specifies which clock source to use for DSP clocking Displays configuration information about a specific voice port or a summary of all voice ports Displays information about the T1 links
Job Aids
These job aids are available to help you complete the lab activity.
PSTN requirements: Framing = ESF Line coding = B8ZS
22
Clock source = line Branch digital:

DS0 group 1 = timeslots 1 to 2, type E&M FGD DS0 group 2 = timeslots 3 to 4, type FGD-EANA
HQ digital = PRI timeslots 1 to 4, type National ISDN
Task 1: Configure the BR T1 CAS Trunk to the PSTN

In this task, you will configure a T1 CAS trunk on the BR router to connect to the PSTN. In the process of configuring the T1 for voice calls, two logical voice ports will be created. You will be able to view these newly created digital voice ports with the same commands as for analog ports.
Activity Procedure
Step 1
Connect the PSTN device to the BR router T1 interface with a crossover T1 cable. Which port is your T1 cable plugged into? _________________ Use the show controller T1 command to view the default settings for framing, line code, and clock source. Note these settings here. Framing ______________________ Line code ______________________ Clock source ____________________
Step 2
Step 3
Configure your T1 controller to complement the settings of the PSTN as shown in the Job Aids section. Use ESF framing and B8ZS line coding. Set the clock source to the PSTN. Verify that the settings match by checking that both controller LEDs are green. Use the show controller T1 command to view status and new settings.
Step 4
When the T1 is functional, create digital voice ports using the DS0-group command. Define CAS group 1 using channels 1 to 2 with E&M FGD signaling. Define CAS group 2 using channels 3 to 4 with FGD-EANA signaling. Use the show commands to verify the newly created digital voice ports. Fill in the information here. How many voice ports were created? ____________ What are the voice port numbers? __________________ How many channels were created? _______________ Which command would you use to view the voice port and the channels? __________________________________________________________ What is the current status of these channels? ______________________
Step 5
Configure a POTS dial peer 1 with an incoming called number ., DID, and no port number.
Lab Guide 23

Step 6
Configure a POTS dial peer 9 with an incoming called number 33X55YXY.. (where X = Pod # and Y = HQ or BR) and DID. Use the voice port previously defined by DS0 group 1. This dial peer will be used for incoming calls from the PSTN to the branch.
The following example is for the pod 1 BR router:

Router(config-dial-peer)# incoming called-number 33155212..
Step 7
Configure a POTS dial peer 97 using destination pattern 9[2-9]....... Use the voice port previously defined by DS0 group 2. This dial peer will be used for seven-digit local dialing from the branch through the PSTN. Configure a POTS dial peer 910 using destination pattern 9[2-9]..[2-9]....... Use the voice port previously defined by DS0 group 2. This dial peer will be used for 10digit local dialing from the branch through the PSTN. Configure a POTS dial peer 9110 using destination pattern 91[2-9]..[2-9]....... Use the voice port previously defined by DS0 group 2. This dial peer will be used for 11digit long distance dialing from the branch to other pod phones through the PSTN. Test this call by dialing 9. You should get a secondary dial tone from the PSTN. You can then dial your 3-, 7- or 10-digit number to complete the call. This is referred to as two-stage dialing. Change dial peers 97, 910, and 9110 so that users can dial 9 plus the 7, 10, or 11 digits without getting a secondary a dial tone. This is referred to as one-stage dialing. What command did you use to enable one-stage dialing? ____________________ What other method could you have used? __________________________________
Step 8
Step 9
Step 10
Step 11
Step 12
Test this functionality by dialing 9 and the 10 or 11 digits and verify that you do not get a secondary dial tone.
You have completed this task when you attain these results:

You have verified the T1 CAS connection to the PSTN. You have verified the existence of the newly created digital voice port or ports. You have placed calls to the PSTN telephone over the CAS with both one-stage and twostage dialing.
24
Task 2: Configure the HQ ISDN PRI Trunk to the PSTN

In this task, you will configure an ISDN PRI trunk connection from HQ to the PSTN.
Activity Procedure
Step 1
Connect the PSTN device to the HQ router T1 interface with a crossover T1 cable. Which port is your T1 cable plugged into? _________________ On the HQ router, ensure that the DSPs are correctly clocked. Specify the correct global ISDN switch type. Use primary-ni. Configure the controller of the T1 PRI PSTN trunk. Use time slots 1-4 and 24. Configure the ISDN signaling interface for inbound voice calls. Configure a POTS dial peer 1 with an incoming called number ., DID, and no port number. Configure a POTS dial peer 9 with an incoming called number 33X55YXY.. (where X = Pod # and Y = HQ or BR) and DID. Use the voice port previously created by the pri-group command during interface configuration mode. This dial peer will be used for incoming calls from the PSTN to the HQ.
Step 2 Step 3 Step 4 Step 5 Step 6
Step 7
The following example is for the pod 1 HQ router:

Router(config-dial-peer)# incoming called-number 33155111..
Step 8
Configure a POTS dial peer 97 using destination pattern 9[2-9]....... Use the voice port previously created by the pri-group command during interface configuration mode. Make sure to strip the leading 9 before sending the call to the PSTN using the forward-digits 7 command. Also make sure that DID is enabled with the directinward-dial command. This dial peer will be used for seven-digit local dialing from the HQ through the PSTN. Configure a POTS dial peer 910 using destination pattern 9[2-9]..[2-9]. Use the voice port previously created by the pri-group command during interface configuration mode. Make sure to strip the leading 9 before sending the call to the PSTN using the forward-digits 11 command. Also make sure that DID is enabled with the direct-inward-dial command. This dial peer will be used for 10-digit local dialing from the HQ through the PSTN. Configure a POTS dial peer 9110 using destination pattern 91[2-9]..[2-9]. Use the voice port previously created by the pri-group command during interface configuration mode. Make sure to strip the leading 9 before sending the call to the PSTN using the forward-digits 11 command. Also make sure that DID is enabled with the direct-inward-dial command. This dial peer will be used for 11-digit longdistance dialing from the HQ through the PSTN. Test this functionality by dialing 9 and the 7- or 10-digit number between your HQ and BR or the 11-digit number to reach the phone of another pod. Use show commands to ensure a PRI channel has been seized.
Step 9
Step 10
Step 11
Step 12

Lab Guide
25

You have verified the HQ T1 PRI connection to the PSTN. You have verified the existence of the newly created digital voice ports. You have placed calls to the PSTN telephone using the HQ ISDN PRI connection.
26
Lab 3-1: Implementing H.323 Gateways

Activity Objective
In this activity, you will configure and verify the operation of H.323 on a gateway. After completing this activity, you will be able to meet these objectives:

Configure H.323 voice service parameters on the HQ and BR gateways Use debug and show commands to monitor the status and progress of call setup procedures in an H.323 environment
Visual Objective
Lab 3-1: Implementing H.323 Gateways

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.08
Required Resources
Pod routers
Command List

Lab Guide
27
H.323 Gateway Configuration Commands

Command Description Enters voice-service-VoIP configuration mode. This command is executed in global configuration mode. Enables gateway configuration. This command is executed in global configuration mode. Enables H.323 signaling for the VoIP service and enters H.323 configuration mode. Configures the timeout value for the response of the outgoing SETUP message. This command is executed in global configuration mode. Shows if the gateway is connected to the gatekeeper. This command is executed in user mode on the gateway. Displays detailed information about the specified dial peer. This command is executed in user mode. Displays a summary of all active dial peers. This command is executed in user mode. Traces the state transition of the H.225 state machine based on the processed event. This command is executed in privileged mode. Displays default debug output for all active POTS dial peers. This command is executed in privileged mode. Displays default debug output for all active VoIP dial peers. This command is executed in privileged mode. Displays H.225 Q931 debug information. This command is executed in privileged mode. Initiates a test call using the gateway to verify call routing. This command is executed in privileged mode.
voice service voip gateway h323 h225 timeout setup <secs>
show gateway show dial-peer voice tag show dial-peer voice summary debug cch323 h225
debug voice dialpeer debug voip dialpeer debug h225 q931 csim start called-number
Job Aids
28
Task 1: Configure an H.323 Gateway

In this task, you will configure voice service parameters on the HQ and BR gateways.
Activity Procedure
Step 1
Modify the default H.323 gateway operation of your HQ and BR routers as H.323 gateways. Change the H.225 setup timeout value to 3 seconds. Make sure you have dial peers that will route extension number calls correctly between the HQ and BR routers in your pod. Establish a voice call to a telephone in your pod. Use the show call active voice command to provide the information that follows: How many and what type of call legs are established? _______________________ Calling number ________________________ Called number ________________________ Remote IP address _____________________ Remote UDP port ______________________
Step 2 Step 3
Step 4
Step 5
Place another call to a telephone outside your own pod. Use the debug cch323 h225 command to provide the information that follows: What is the source address of the call? ____________________________ What is the destination address of the call? ________________________

You have configured and verified that your gateway is configured for H.323. The out from the show gateway command should resemble the following:
router# show gateway H.323 ITU-T Version: 4.0 H.323 service is up This gateway is not registered to any gatekeeper H323 Stack Version: 0.1
Alias list (CLI configured) E164-ID 1003 E164-ID 1001 E164-ID 1002 Alias list (last RCF) is empty H323 resource thresholding is Disabled
Lab Guide
29
Lab 3-2: Implementing SIP Gateways

Activity Objective
In this activity, you will use SIP direct call procedures (UA to UA) to establish VoIP calls. After completing this activity, you will be able to meet this objective:
Configure dial peers to use SIP call control procedures to set up VoIP calls
Visual Objective
Lab 3-2: Implementing SIP Gateways

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.09
Required Resources

Pod routers IP phones
Command List
30
SIP Gateway Configuration Commands

Command Description Enters VoIP configuration mode. Enables SIP signaling for the VoIP service and enters SIP configuration mode. Specifies SIP to be the protocol used on the VoIP dial peer. Displays active SIP calls. Displays various real-time SIP call information. This command is executed in privileged mode.
voice service voip sip session protocol sipv2 show sip-ua calls debug ccsip options
Job Aids
Task 1: Configure a Gateway for SIP

In this task, you will configure your router to initiate calls with the router of your partner using SIP. For this activity, you will use SIP direct (UA to UA).
Activity Procedure
Step 1 Step 2
On the HQ and BR routers, enable SIP services. Modify the existing VoIP dial peers that point to the telephones belonging to your partner to use direct call connect (UA to UA) SIP call control procedures when establishing voice calls. For direct calls, the IP address in the session target command will be a valid address of your HQ or BR router. Use the show call active voice command to verify that you now have SIP call legs when placing a call to a partner telephone. Enable SIP debugging and place a call between your telephone and a partner telephone. Observe the call setup, capabilities negotiation, and assignment of ports for the call. Investigate the status of SIP with variations of the show sip-ua command.
Step 3
Step 4
Step 5

You have established voice calls between telephones connected to your routers by way of direct SIP call control procedures. While a call from a local phone to a remote site is active, the show sip-ua calls command will display an active call. Your output should resemble the following:
HQ-1# show sip-ua calls SIP UAC CALL INFO Number of SIP User Agent Client(UAC) calls: 0

Lab Guide
31
SIP UAS CALL INFO Call 1 SIP Call ID 6A8F4AD@10.10.10.2 State of the call Substate of the call Calling Number Called Number Bit Flags CC Call ID : D215F304-7B5A11DC-8005EA1A: STATE_ACTIVE (7) : SUBSTATE_NONE (0) : 2818902001 : 1003 : 0x1212003A 0x100000 0x488 : 1
Source IP Address (Sig ): 10.10.10.1 Destn SIP Req Addr:Port : 10.10.10.2:5060 Destn SIP Resp Addr:Port: 10.10.10.2:56884 Destination Name : 10.10.10.2
Number of Media Streams : 1 Number of Active Streams: 1 RTP Fork Object Media Stream 1 State of the stream Stream Call ID Stream Type Negotiated Codec Codec Payload Type Negotiated Dtmf-relay Dtmf-relay Payload Type : STREAM_ACTIVE : 1 : voice-only (0) : g729r8 (20 bytes) : 18 : inband-voice : 0 : 0x0
Media Source IP Addr:Port: 10.10.10.1:18050 Media Dest IP Addr:Port : 10.10.10.2:16522
Orig Media Dest IP Addr:Port : 0.0.0.0:0
Number of SIP User Agent Server(UAS) calls: 1
32
Lab 4-1: Implementing Numbering Plans

Activity Objective
In this activity, you will design a basic numbering plan composed of PSTN access codes, site codes, extensions, and dialing prefixes, and build out the numbering plan using dial peers. After completing this activity, you will be able to meet these objectives:

Design a private numbering plan Use site codes to route calls between sites
Visual Objective
Lab 4-1: Implementing Numbering Plans

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.010
Required Resources
No new resources are required.
Command List

Lab Guide
33
Numbering Plan Commands

Command Description Enters dial-peer configuration mode and specifies VoIP Specifies the destination IP address for the gateway terminating a VoIP call Configures a telephone number for this dial peer Defines a voice translation rule for voice calls Defines a rule within a voice translation rule
dial-peer voice tag voip session target ipv4:x.x.x.xSyntax Content Text style destination-pattern string voice translation-rule rule-tag rule precedence /match/ /replace/ [type {matchtype replace-type} [plan {match-plan replaceplan}]] voice translation-profile profile-name translate {called | calling | redirect-called} translation-rule-number translation-profile {incoming | outgoing} name test voice translationrule number input-teststring [type match-type [plan match-type]
Specifies a translation profile for all incoming VoIP calls Associates a translation rule with a voice translation profile
Assigns a translation profile Tests the functionality of a translation rule
34
Job Aids
These job aids are available to help you complete the lab activity. Site Access Code and Site Numbers
Router HQ1 BR1 HQ2 BR2 HQ3 BR3 HQ4 BR4 HQ5 BR5 HQ6 BR6 Site Access Code 8 8 8 8 8 8 8 8 8 8 8 8 Site Number 11 12 21 22 31 32 41 42 51 52 61 62
Telephone Numbers and Site Codes

Phone HQ IP phone 1 HQ IP phone 2 HQ IP analog phone 1 HQ IP analog phone 2 BR IP phone BR analog phone Telephone Number Site Code

Lab Guide
35
Task 1: Configure a Numbering Plan for HQ and Branch Offices

In this task, you will create a basic numbering plan for the HQ and branch offices. The HQ and branch sites should have different site codes so that users may dial either site using a site code and extension.
Activity Procedure
Step 1
Assign extensions to phones in your pod. Use the Classroom Dial Plan (at the beginning of this lab guide) for the extension numbers for your pod. Assign site codes to the HQ and branch sites. Use the Site Access Code and Site Numbers table (in the Job Aids section of this lab) for site access codes for your pod. Configure dial peers on the HQ and BR routers according to the numbering plan.
Use dial peers and voice translation patterns to simplify the implementation.
Step 2
Step 3
Note
Users can call other users at the same site using the extension numbers and they can call remote site users using a combination of the site access code and the appropriate site number to create a unique site code for each site.
36
Lab 4-2: Implementing PSTN Dial Plans

Activity Objective
In this activity, you will implement a proper PSTN dial plan to ensure correct DNIS, ANI, and TON type presentation for inbound and outbound PSTN calls on a gateway. After completing this activity, you will be able to meet these objectives:

Configure dial peers for inbound and outbound PSTN routing Configure voice translation rules and profiles for correct ANI and DNI digit manipulation
Visual Objective
Lab 4-2: Implementing PSTN Dial Plans

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.011
Required Resources

IP phones PSTN phones
Command List

Lab Guide
37
Digit Manipulation Commands

Command Description Strips all the digits that explicitly match a POTS dial peer. Digit stripping is enabled by default on POTS dial peers. Specifies the prefix of the dialed digits for a dial peer. Specifies which digits to forward for voice calls. Defines how to expand a telephone extension number into a particular destination pattern. Defines a voice translation rule for voice calls. Defines a rule within a voice translation rule.
digit-strip
prefix digits forward-digits [0-32]|all|extra num-exp dialed-digits substitution voice translation-rule rule tag rule precedence /match/ /replace/ [type {match-type replace-type} [plan {match-plan replace-plan}]] voice translation-profile profile-name translate {called | calling | redirect-called} translationrule-number translation-profile {incoming | outgoing} name test voice translation-rule number input-test-string [type match-type [plan match-type]
Specifies a translation profile for all incoming VoIP calls. Associates a translation rule with a voice translation profile. Assigns a translation profile. Tests the functionality of a translation rule.
Call Routing and Path Selection Commands

Command Description Specifies either the prefix or the full E.164 telephone number to be used for a dial peer. Specifies a digit string that can be matched by an incoming call to associate the call with a dial peer. Specifies the full E.164 telephone number to be used to identify the dial peer of an incoming call. Enables the DID call treatment for an incoming called number. Indicates the preferred order of a dial peer within a hunt group. Checks the status of outbound POTS dial peers during call setup and to disallow, for that call, any dial peers whose status is down.
destination-pattern [+]string[T] incoming called-number [+]string[T] answer-address [+]string[T] direct-inward-dial preference [0-9] no dial-peer outbound statuscheck pots
Job Aid
This job aid is available to help you complete the lab activity.
Voice configuration library at: http://www.cisco.com/en/US/products/ps6441/prod_configuration_guide09186a0080565f8 a.html

38
Task 1: Configure Dial Peers

In this task, you will configure dial peers for inbound and outbound PSTN routing.
Activity Procedure
Step 1 Step 2
Verify that the controllers and voice ports are configured correctly. On the HQ and BR gateways, configure or verify the incoming PSTN dial peers have the incoming called number 33X55XXX.. format and DID. Use the port that connects to the PSTN for this dial peer. On the HQ and BR gateways, configure or verify these dial peers using the T1 PSTN trunk:
Step 3
Local calls: Dial peer 97, destination pattern 9[2-9]...... Dial peer 910, destination pattern 9[2-9]..[2-9]......
National calls: dial peer 9110, destination pattern 91[2-9]..[2-9]...... International calls: dial peer 9011, destination pattern 9011T Services: Emergency services:

Dial peer 911, destination pattern 911 Dial peer 9911, destination pattern 9911
Directory services: dial peer 411, destination pattern 9411 Repair services: dial peer 611, destination pattern 9611

You can place and receive PSTN calls. Callers can access emergency services by dialing 911 or 9911. Callers can access directory and repair services by dialing 411 and 611. Callers can place international calls by dialing 9011 plus any combination of digits.
Task 2: Configure Digit Manipulation

In this task, you will configure voice translation rules and profiles for correct ANI and DNIS digit manipulation.
Activity Procedure
Step 1
Use the following configuration commands to remove the automatic number translation function that is used by Cisco Unified Communications Manager Express, where X is your pod number:

Lab Guide
39
telephony-service no dialplan-pattern 1 33X555X2.. extension-length 4

Step 2
On the HQ gateway, configure a voice translation profile pstn-in that performs these digit manipulations:

Any calling number starting with 33X should be prefixed with 91 so that a user may use the missing directory number to dial that number back. The called DID numbers 33X55XX should be cut down to the four-digit extension. For example, 3315511101 should be modified to 1101.
Step 3
Bind the voice translation profile pstn-in to the T1 PSTN trunk. The profile should be applied to incoming calls. Verify that inbound PSTN calls are working again. Configure a voice-translation profile pstn-out that performs this digit manipulation:
Step 4
The calling number 1 should be prefixed with the gateway DID range 33X555. For example, if a call is placed from HQ phone 1-1, the calling number should be modified from 1101 to 3315551101.
Step 5
Bind the voice translation profile pstn-out to the T1 PSTN trunk. The ANI should now be correctly modified to include the DID range for outgoing calls. Complete the same exercise on the BR router by repeating Steps 1 through 5, and assign the pstn-in profile to voice port 0/0/0:1 and the pstn-out profile to voice port 0/0/0:2.
Step 6

Inbound calls to HQ and BR should include 91 in the calling number. For example, a call from the PSTN 3345554101 to HQ-1 phone 1-1 should be displayed as 913345554101. Outbound calls from HQ-1 should have the calling number 33155511XX.
40
Lab 4-3: Configuring Path Selection

Activity Objective
In this activity, you will implement toll bypass and other path selection techniques. You will also experiment with two different configurations to control hunt capabilities. After completing this activity, you will be able to meet this objective:
Create a hunt group using the preference command and determine hunting behavior
Visual Objective
Lab 4-3: Configuring Path Selection

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
Primary Path Backup Path
POD-1
POD-x
CVOICE v6.012
Required Resources

One PSTN device per pod One telephone per pod
Command List

Lab Guide
41
Hunt Group Commands

Command Description Displays real-time voice port module signaling; displays digits as they are received by the voice port Configures a telephone number for this dial peer Specifies a hunt selection order for dial peers Enters dial-peer configuration mode Specifies which digits to forward for voice calls Specifies the port for a dial peer Specifies the preferred order of a dial peer within a hunt group Disables all dial-peer hunting if a call fails on the specified dial peer Displays information on active calls Displays dial-peer configuration information. Displays which dial peer is matched when a particular telephone number is dialed Displays summary information on active calls
debug vpm signal destination-pattern string dial-peer hunt 0-7 dial-peer voice tag pots forward-digits port port-number preference 0-9 huntstop show call active voice show dial-peer voice (tag)|(summary) show dialplan number number show voice call summary
Job Aid
Voice configuration library at: http://www.cisco.com/en/US/products/ps6441/prod_configuration_guide09186a0080565f8 a.html
Task 1: Configure Hunt Groups

In this task, you will configure a hunt group to send calls to both of your locally terminated telephones using the same number.
Activity Procedure
Step 1
For the hunt group number, you will use the same first three digits as your telephones are now configured for. The fourth digit will be 9. For example, if your telephone numbers are 1103 and 1104, you will use 1109 as the hunt group number. Write your hunt group number here. Hunt group number ______________________
Step 2 Step 3
Ensure that both telephones are still connected to your router voice ports. Configure additional dial peers for your local FXS ports to reach both voice ports using the same new hunt group number for each dial peer. Do not edit existing dial peers for this activity because they will be needed for future labs. This means that
42
you will have two new dial peers, each for the same hunt group number (such as 1109), assigned to each of your FXS ports.
Step 4
To properly test the hunt behavior between your two phones, you will use the PSTN telephone. To reach the hunt group number from the PSTN phone, dial the sevendigit PSTN number of the hunt group number. Repeat this many times, taking note of any patterns as to how calls are allocated to each telephone. The default behavior at this point will be random choosing of a port. However, to demonstrate this randomness with only two telephones, you may have to make a number of calls. One method that is used to control the order of hunting is through the use of the preference command. What is the default setting for preference on a dial peer? _____________ Which command did you use to verify the setting? _______________________ Change the preference on one of your hunt dial peers to 1. Which setting is preferred, the 0 or 1 setting? ___________________ Test the hunt group again by calling several times, making note of which telephone rings first. Is this what you expected? Now take the preferred telephone off hook and dial the hunt group number again. Did the other telephone ring? ________________ On the dial peer with the preference set to 0, change the preference to 2. Which telephone should always ring first? Test the hunt group again. Is the outcome what you expected? _______________________________________________________
Step 5
Step 6
You can configure hunt behavior for all dial peers globally with the dial-peer hunt command. Before changing this setting, find out what the default setting is and note it here. Default dial-peer hunt setting _______________________ Which command did you use to view this? ___________________________ Configure the dial-peer hunt setting to 7. How do you expect your hunt group to choose which telephone to ring now? Test the hunt group again. Is the outcome what you expected? ________________________________________________________
Step 7
Delete the dial peers you created for the hunt groups.
You can control your hunt group behavior and explain how each command works.
Task 2: Configure Redundant Calling Paths

In this task, you will configure redundant calling paths between your BR and HQ gateways.
Activity Procedure

Lab Guide
43
Step 1
In case the WAN is down, you will need a dial peer that points directly to the PSTN. Create a dial peer that points to the PSTN but that will not be used unless the IP WAN is down or congested. This enables redundant calling paths between sites. Test that calls are going across the primary path (the WAN) between HQ and BR. Shut down the IP connection between the HQ and BR and test that calls are going across the PSTN. Bring the serial port back up.
Step 2 Step 3
Step 4
The ISDN path is being used only when the WAN is down or congested.
Task 3: Configure TEHO

In this task, you will configure TEHO to the PSTN phone of your partner.
Activity Procedure
Step 1
To configure TEHO, you will create a dial peer to route PSTN calls to your partner pod PSTN telephone. Write down the number of your partner pod PSTN phone. What is your partner pod PSTN phone number? ________________________
Step 2
Create a dial peer that will route calls to your partner pod PSTN phone through the IP WAN instead of the PSTN. Test by placing a call to the PSTN phone of your partner.
Step 3
The WAN path is being used when you call the PSTN phone of your partner.
44
Lab 4-4: Implementing Calling Privileges

Activity Objective
In this activity, you will implement calling privileges on a gateway using COR. After completing this activity, you will be able to meet these objectives:

Prepare the dial peers for COR and create COR labels Create COR lists and assign members Assign COR lists to the appropriate dial peers
Visual Objective
Lab 4-4: Implementing Calling Privileges

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.013
Required Resources

IP phones PSTN phone
Command List

Lab Guide
45
COR Commands
Command Description Specifies that named class of restrictions (COR) apply to dial peers Creates a named COR Defines a COR list name Specifies the COR list to be used when a specified dial peer acts as the incoming dial peer Specifies the COR list to be used by outgoing dial peers
dial-peer cor custom name cor-name dial-peer cor list listname corlist incoming cor-listname corlist outgoing cor-listname
Job Aid
Phone number for international calls: 90113337775555
Task 1: Create COR Labels

In this task, you will configure COR labels. Four different classes will be required: emergency, local, national, and international.
Activity Procedure
Step 1
On the HQ gateway, verify that you have a unique dial peer for local calls, national calls, international calls, and emergency calls. Create these COR labels:

Step 2
local ld intl 911 int
Use the show dial-peer cor command to verify your configuration. Your output should resemble the following example:
router# show dial-peer cor
Class of Restriction name: 911 name: local name: ld

name: intl name: int
Task 2: Configure COR Lists

In this task, you will create COR lists and assign members. Complete these steps:
Step 1
Configure the incoming COR lists and members:

key-int: int key-local: int, local, 911 key-ld: int, local, 911, ld key-intl: int, local, 911, ld, intl
Step 2
Configure the outgoing COR lists and members:

lock-911: 911 lock-int: int lock-local: local lock-ld: ld lock-intl: intl
Use the show dial-peer cor command to verify your configuration. Your output should resemble this.
router# show dial-peer cor
Class of Restriction name: 911 name: int name: local name: ld name: intl
COR list key-int member: int
COR list key-local member: local member: 911 member: int

Lab Guide
47
COR list key-ld member: local member: 911 member: int member: ld
COR list key-intl member: local member: 911 member: int member: ld member: intl
COR list lock-int member: int
COR list lock-911 member: 911
COR list lock-local member: local
COR list lock-ld member: ld
COR list lock-intl member: intl
48
Task 3: Configure Dial Peers to Use COR Lists

In this task, you will assign COR lists to the appropriate dial peers. A user with the local class should not be able to place any national or international calls, a user with the national class should not be able to place any international calls, and a user with the international class should be able to place any call. Complete these steps:
Step 1
Assign these outgoing COR lists to the appropriate PSTN dial peers:

lock-int lock-local lock-ld lock-911 lock-intl
Step 2
Apply the COR list to the individual analog phones. Assign the incoming national COR list to the line of phone Phone3-1 and the incoming international COR list to the line of phone Phone4-1. (Optional) Apply the COR list to the individual ephone-dns. Assign the incoming national COR list to the line of phone Phone1-1 and the incoming international COR list to the line of phone Phone2-1. Create the COR members and COR lists on the BR router and apply the same method to the IP and analog phones.
Step 3
Step 4

You cannot place international calls using Phone1-1, Phone3-1, and Phone5-1. You can call any PSTN destination using Phone2-1, Phone4-1, and Phone6-1.

Lab Guide
49
Lab 5-1: Configuring Basic Gatekeeper Functionality

Activity Objective
In this activity, you will configure the corporate gatekeeper Corp-GK as a gatekeeper controlling two zones: HQ and BR. Call routing between San Jose and Chicago will be done via the gatekeeper. After completing this activity, you will be able to meet these objectives:

Configure an H.323 gatekeeper to support multiple local zones Register gateways at the gatekeeper Test the gatekeeper configuration and gateway registration
Visual Objective
Lab 5-1: Configuring Basic Gatekeeper Functionality

Phone1-1 7941/61
Two-Pod Group
GK1 GK2
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.014
Required Resources

Corporate gatekeeper Corp-GK HQ phones BR phones
50
Command List
The table describes the commands that are used in this activity. Gatekeeper Configuration Commands
Command Description Enters gatekeeper configuration mode Specifies a zone controlled by a gatekeeper Brings the gatekeeper online Adds a prefix to the gatekeeper zone list
gatekeeper zone local zone-name domain-name [ras-IP-address] no shutdown zone prefix gatekeeper-name e164-prefix [blast | seq] [gwpriority priority gw-alias [gwalias, ...]]
gw-type-prefix type-prefix [hopoff gkid1] [hopoff gkid2] [hopoff gkidn] [seq | blast] [default-technology] [gw ipaddr ipaddr [port]]
Adds a technology prefix to the gatekeeper configuration list
show gatekeeper calls show gatekeeper status
Displays the status of each ongoing call of which a gatekeeper is aware Displays the overall gatekeeper status, including the authorization and authentication status and zone status Displays the status of all registered endpoints for a gatekeeper Displays the gateway technology prefix table Displays the zone prefix table Displays the status of zones related to a gatekeeper
show gatekeeper endpoints show gatekeeper gw-type-prefix show gatekeeper zone prefix [all] show gatekeeper zone status
Gateway Configuration Commands

Command Description Enters gateway configuration mode and enables the gateway to register with a gatekeeper Identifies this as a VoIP gateway interface Defines the name and location of the gatekeeper for this gateway
gateway h323-gateway voip interface h323-gateway voip id gatekeeperid {ipaddr ip-address [port]| multicast} [priority priority]

Lab Guide
51
Command
Description Defines the H.323 name of the gateway, identifying this gateway to its associated gatekeeper Defines the numbers that are used as the technology prefix that the gateway registers with the gatekeeper Enables RAS signaling; meaning that a gatekeeper is consulted to translate the E.164 address into an IP address
h323-gateway voip h323-id interface-id h323-gateway voip tech-prefix prefix
session target ras
Job Aid
Gatekeeper address: Fa0/0.103-10.X.3.102
Task 1: Configure Local Zones

In this task, you will configure an H.323 gatekeeper to support multiple local zones. You will also configure appropriate dial plan information for the gatekeeper to resolve calls between sites San Jose and Chicago.
Activity Procedure
Step 1
On the HQ gateway, configure a gatekeeper using these parameters:

Local zone HQ, domain cisco.com, IP address of loopback 0 interface Local zone BR, domain cisco.com
Step 2
Enable the gatekeeper process.

The HQ-GK gatekeeper is up and running with two local zones: HQ and BR. The output from a show gatekeeper status command should resemble the following:
HQ-1# show gatekeeper status Gatekeeper State: UP Load Balancing: Flow Control: Zone Name: Zone Name: Accounting: DISABLED DISABLED HQ BR DISABLED DISABLED
Endpoint Throttling: Security: DISABLED
Maximum Remote Bandwidth:
unlimited
52
Current Remote Bandwidth:
0 kbps
Current Remote Bandwidth (w/ Alt GKs): 0 kbps
Task 2: Configure Zone and Technology Prefixes

In this task, you will configure technology prefixes and interzone routing on the San Jose gatekeeper. Call routing will use the site extension range. For example, any call starting with 1 should be routed to the HQ zone, and any call starting with 2 should be routed to the BR zone.
Activity Procedure
Step 1
On the HQ gatekeeper, configure the zone prefix for the HQ zone. Any call to a San Jose extension starting with 11 should be routed to this zone. On the HQ gatekeeper, configure the zone prefix for the BR zone. Any call to a Chicago extension starting with 12 should be routed to this zone. Configure a default gateway technology prefix of 1#.
Step 2
Step 3

The zone prefixes for the HQ and BR zones are configured correctly. The default technology prefix is 1#. The output from a show gatekeeper zone prefix command should resemble the following:
HQ-1# show gatekeeper zone prefix ZONE PREFIX TABLE ================= GK-NAME ------HQ BR E164-PREFIX ----------11.. 12..
Task 3: Configure Gateways to Register with a Gatekeeper

In this task, you will configure the gateway in Chicago to register with the gatekeeper in San Jose.
Activity Procedure
Step 1
Using the bulleted items here, configure your router as an H.323 gateway. Analyze the debug command output to observe the interactions between your router and the gatekeeper. These tasks are necessary to register with a gatekeeper:
Configure your router to be a gateway.

Lab Guide
53
Specify which interface IP address will be used to register with the gatekeeper and also specify the identity of the gatekeeper. Use your Ethernet interface for gateway configuration. Specify an H.323 ID for your gateway by combining gw with your pod and router number. For example, if you were pod 1 with the HQ router, your H.323 ID would be gwP1HQ. Use the show gateway command on your router to verify that you have registered with the gatekeeper.
What is the gatekeeper name you have registered with? ______________________ Under the CLI alias list, which numbers register with the gatekeeper? ___________
Step 2
On the HQ router, configure the H.323 gateway process. The gateway should register with zone HQ and technology prefix 1#. Use the loopback interface as the H.323 source interface and ensure that you configure a proper H.323 gateway ID. Connect to the gatekeeper and use variations of the show gatekeeper command to verify that your router is registered and that your router has registered the destination patterns from your POTS dial peers. Which IP address is registered to be used for calls to your device? ______________ Which port number is being used for call signaling? __________________________ What is the H.323 ID of your router? ________________________________ Which zone is your gateway part of? __________________________
Step 3
Step 4
Reconfigure the existing VoIP dial peers that point to Chicago. Instead of routing directly to Chicago, the call should be routed to the corporate gatekeeper Corp-GK. Remove the redundant second VoIP dial peer. Create a dial peer to use RAS for all calls to destinations outside the zone. Ensure that Cisco Unified Communications Manager Express does not register any ephone-dn with the gatekeeper. On the BR router, configure the H.323 gateway process. The gateway should register with zone BR. Use the loopback interface as the H.323 source interface and ensure that you configure a proper H.323 gateway ID. Create a dial peer to use RAS for all calls to destinations outside the zone.
Step 5 Step 6
Step 7
Step 8

The HQ gateway is registered at the gatekeeper with a technology prefix of 1#. Calls between the San Jose and Chicago sites are possible via the gatekeeper. The output of a show gatekeeper endpoints command should resemble the following:
HQ-1# show gatekeeper endpoints GATEKEEPER ENDPOINT REGISTRATION ================================

CallSignalAddr
Port
RASSignalAddr
Port
Zone Name
Type ---H323-GW
Flags -----
--------------- ----- --------------- ----- --------10.1.250.101 1720 10.1.250.101 58963 HQ
H323-ID: GW-P1HQ E164-ID: 1101 E164-ID: 1102 Voice Capacity Max.= 10.1.250.102 1720 Avail.= Current.= 0 58306 BR VOIP-GW
10.1.250.102
H323-ID: GW-P1BR E164-ID: 1201 E164-ID: 1202 Voice Capacity Max.= Avail.= Current.= 0
Total number of active registrations = 2

Lab Guide
55
Lab 5-2: Implementing Gatekeeper-Based CAC

Activity Objective
In this activity, you will configure the corporate gatekeeper to use CAC between SJC and CHI. After completing this activity, you will be able to meet these objectives:

Calculate the required zone bandwidth for a given scenario given call requirements Configure zone bandwidth to enable proper CAC
Visual Objective
Lab 5-2: Implementing Gatekeeper-Based CAC

Phone1-1 7941/61
Two-Pod Group
GK1 GK2
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1
l ria Se T1/E 1
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.015
Required Resources

Corporate gatekeeper Corp-GK set up for call routing between San Jose and Chicago San Jose IP phones Chicago IP phones
Command List
56
Gatekeeper Configuration Commands

Command Description Specifies the maximum aggregate bandwidth for H.323 traffic and verifies the available bandwidth of the destination gatekeeper. For interzone and total bandwidth, the range is from 1 to 10,000,000. For session bandwidth, the range is from 1 to 5000.
bandwidth {interzone | total | session} {default | zone zone-name} bandwidth-size
show gatekeeper calls show gatekeeper status show gatekeeper endpoints show gatekeeper gw-typeprefix show gatekeeper zone prefix [all] show gatekeeper zone status
Displays the status of each ongoing call of which a gatekeeper is aware. Displays the overall gatekeeper status, including the authorization and authentication status and zone status. Displays the status of all registered endpoints for a gatekeeper. Displays the gateway technology prefix table. Displays the zone prefix table. Displays the status of zones related to a gatekeeper.
Gateway Configuration Commands

Command Description Configures a gateway to report H.323 resource availability to its gatekeeper. Displays the threshold configuration settings and status for an H.323 gateway.
resource threshold [all] [high percentage-value] [low percentage-value] show call resource voice threshold
Job Aids

Lab Guide
57
Task 1: Calculate Bandwidth Requirements

In this task, you will calculate the bandwidth requirements for one G.711 call from the San Jose site to the Chicago site.
Activity Procedure
Complete this step:
Step 1
Calculate the bandwidth for the one G.711 call.
You have calculated the correct bandwidth for one G.711 call in a H.323 gatekeeper network.
Task 2: Configure Zone Bandwidth

In this task, you will configure the correct zone bandwidth for calls from the San Jose zone to the Chicago zone.
Activity Procedure
Complete this step:
Step 1
On the HQ gatekeeper, configure the interzone bandwidth for one G.711 call for the HQ zone and the BR zone.
The correct bandwidth is configured on the gatekeeper. Create a call from any phone in San Jose to a phone in Chicago. Use the debug h225 asn1 and the show gatekeeper status commands to verify correct bandwidth operation. Place a second call between from Chicago to San Jose. The call should be rejected and routed over the PSTN.
58
Lab 6-1: Configuring a Cisco UBE

Activity Objective
In this activity, you will configure a Cisco UBE to connect to an ISP. After completing this activity, you will be able to meet this objective:
Configure a Cisco UBE for protocol interworking and address hiding
Visual Objective
Lab 6-1: Configuring a Cisco UBE

Phone1-1 7941/61
Two-Pod Group
Phone1-x 7941/61
Phone2-1 7941/61
Phone2-x 7941/61
IP WAN
Phone3-1 1101
HQ-1 SIP
IP IP
HQ-2
Phone4-1 1102
PSTN BR-1
FXS
Phone5-1 7941/61
BR-2
FXS
PSTN Phone-1
PSTN Phone-x
Phone5-x 7941/61
POD-1
POD-x
CVOICE v6.016
Required Resources

HQ-1 H.323 gateway router1 HQ-2 H.323 gateway router2
Command List

Lab Guide
59
IP-to-IP Gateway Configuration Commands

Command Description Enables protocol interworking on an IP-to-IP gateway. Configures how media streams are handled on an IP-to-IP gateway in dial-peer, voice-class, or voice-service configuration mode. Enables codec capabilities to be passed transparently between endpoints on an IP-to-IP gateway. This can also be configured in a voice class.
allow-connections fromtype to to-type media [flow-around | flowthrough] codec transparent
Job Aids
Task 1: Configure a Cisco UBE for Protocol Interworking and Address Hiding
In this task, you will configure the San Jose gateway router to also act as a Cisco UBE. Calls to a SIP carrier will travel through the Cisco UBE, with H.323 being the internal call leg.
Activity Procedure
Step 1 Step 2 Step 3 Step 4
On the San Jose gateway router, shut down the gatekeeper process. On the San Jose gateway router, enable interworking between H.323 and SIP. Ensure that the loopback 0 interface is used for H.323 signaling. Create a new outbound SIP VoIP dial peer that will route calls to the SIP carrier. The destination pattern should be a 9011T, G.711 mu-law codec.
You can place a call from San Jose to the international PSTN phone. Use the show call active voice brief command to verify H.323-to-SIP interworking.
60
Answer Key
The correct answers and expected solutions for the activities that are described in this guide appear here.
Lab 2-1 Answer Key: Configuring Analog Voice Interfaces

When you complete this activity, your configuration will be similar to the results here, with differences that are specific to your device or workgroup:
! voice-port 0/2/1 cptone AU ring cadence pattern AU !

Lab Guide
61
Lab 2-2 Answer Key: Configuring POTS Dial Peers

HQ Router
! dial-peer voice 1103 pots destination-pattern 1103 port 0/2/0 ! dial-peer voice 1104 pots destination-pattern 1104 port 0/2/1 !
BR Router
! dial-peer voice 1202 pots destination-pattern 1202 port 0/0/0 !
62
Lab 2-3 Answer Key: Configuring VoIP Dial Peers

HQ
! voice class codec 1 codec preference 1 g711ulaw codec preference 2 g729r8 ! dial-peer voice 1200 voip destination-pattern 12.. voice-class codec 1 session target ipv4:10.1.4.102 !
BR
! voice class codec 1 codec preference 1 g711ulaw codec preference 2 g729r8 ! dial-peer voice 1100 voip destination-pattern 11.. voice-class codec 1 session target ipv4:10.1.4.101 !

Lab Guide
63
Lab 2-4 Answer Key: Configuring Digital Voice Interfaces

Implementing CAS Trunks on BR
When you complete this task, your configuration will be similar to the results here, with differences that are specific to your device or workgroup:
Cisco IOS Configuration: T1 CAS

network-clock-participate wic 0 network-clock-select 1 T1 0/0/0 ! controller T1 0/0/0 framing esf linecode b8zs clock source line ds0-group 1 timeslots 1-2 type e&m-fgd ds0-group 2 timeslots 3-4 type fgd-eana !
Two-Stage Dialing
dial-peer voice 3315511200 pots incoming-called-number 33155112.. direct-inward-dial port 0/0/0:1 ! dial-peer voice 97 pots destination-pattern 9[2-9]...... port 0/0/0:2 ! dial-peer voice 910 pots destination-pattern 9[2-9]..[2-9]...... port 0/0/0:2 ! dial-peer voice 9110 pots destination-pattern 91[2-9]..[2-9]...... port 0/0/0:2 !
64
One-Stage Dialing
! dial-peer voice 97 pots destination-pattern 9[2-9]...... forward-digits 7 port 0/0/0:2 ! dial-peer voice 910 pots destination-pattern 9[2-9]..[2-9]...... forward-digits 10 port 0/0/0:2 ! dial-peer voice 9110 pots destination-pattern 91[2-9]..[2-9]...... forward-digits 11 port 0/0/0:2 !
Implementing PRI Trunks on HQ

When you complete this task, your configuration will be similar to the results here, with differences that are specific to your device or workgroup:
Cisco IOS Configuration: T1 PRI

network-clock-participate wic 0 network-clock-select 1 T1 0/0/0 ! isdn switch-type primary-ni ! controller T1 0/0/0 framing esf linecode b8zs pri-group timeslots 1-4 ! interface serial 0/0/0:23 isdn incoming-voice voice ! dial-peer voice 3315511100 pots incoming-called-number 33155111.. direct-inward-dial port 0/0/0:23 !
Lab Guide
65
dial-peer voice 97 pots destination-pattern 9[2-9]...... forward-digits 7 port 0/0/0:23 ! dial-peer voice 910 pots destination-pattern 9[2-9]..[2-9]...... direct-inward-dial forward-digits 10 port 0/0/0:23 ! dial-peer voice 9110 pots destination-pattern 91[2-9]..[2-9]...... forward-digits 11 port 0/0/0:23 ! dial-peer voice 1 pots incoming-called-number . direct-inward-dial !
66
Lab 3-1 Answer Key: Implementing H.323 Gateways

HQ
voice service voip h323 h225 timeout setup 3 ! gateway ! interface Loopback 0 ip address 10.1.250.101 255.255.255.0 h323-gateway voip interface h323-gateway voip bind srcaddr 10.1.250.101 !
BR
voice service voip h323 h225 timeout setup 3 ! gateway ! interface Loopback 0 ip address 10.1.250.102 255.255.255.0 h323-gateway voip interface h323-gateway voip bind srcaddr 10.1.250.102

Lab Guide
67
Lab 3-2 Answer Key: Implementing SIP Gateways

HQ
voice service voip sip ! dial-peer voice 2000 voip destination-pattern 12.. session protocol sipv2 session target ipv4:10.1.250.102
BR
voice service voip sip ! dial-peer voice 1000 voip destination-pattern 11.. session protocol sipv2 session target ipv4:10.1.250.101
68
Lab 4-1 Answer Key: Implementing Numbering Plans

HQ
voice translation-rule 1200 rule 1 /^812/ // ! voice translation-profile strip-sites translate called 1200 ! dial-peer voice 812 voip translation-profile outgoing strip-sites destination-pattern 81212.. session target ipv4:10.1.4.102 !
BR
voice translation-rule 1100 rule 1 /^811/ // ! voice translation-profile strip-sites translate called 1100 ! dial-peer voice 811 voip translation-profile outgoing strip-sites destination-pattern 81111.. session target ipv4:10.1.4.101

Lab Guide
69
Lab 4-2 Answer Key: Implementing PSTN Dial Plans on Cisco IOS Gateways
HQ
voice translation-rule 1000 rule 1 /^331551/ // ! voice translation-rule 1001 rule 1 /.*/ /91\0/ ! voice translation-rule 1003 rule 1 /11../ /331551\0/ ! voice translation-profile pstn-in translate calling 1001 translate called 1000 ! voice translation-profile pstn-out translate calling 1003 ! voice-port 0/0/0:23 translation-profile incoming pstn-in translation-profile outgoing pstn-out ! dial-peer voice 97 pots destination-pattern 9[2-9]...... incoming called-number 33155111.. direct-inward-dial port 0/0/0:23 forward-digits 7 ! dial-peer voice 910 pots destination-pattern 9[2-9]..[2-9]...... incoming called-number 33155111.. direct-inward-dial port 0/0/0:23 forward-digits 10
70
dial-peer voice 9110 pots destination-pattern 91[2-9]..[2-9]...... incoming called-number 33155111.. direct-inward-dial port 0/0/0:23 forward-digits 11 ! dial-peer voice 9011 pots destination-pattern 9011T port 0/0/0:23 prefix 011 ! dial-peer voice 911 pots destination-pattern 911 no digit-strip port 0/0/0:23 ! dial-peer voice 9911 pots destination-pattern 9911 port 0/0/0:23 prefix 911 ! dial-peer voice 411 pots destination-pattern 9411 forward-digits 3 port 0/0/0:23 ! dial-peer voice 611 pots destination-pattern 9611 forward-digits 3 port 0/0/0:23
BR#
voice translation-rule 1000 rule 1 /^331552/ // ! voice translation-rule 1001 rule 1 /.*/ /91\0/ ! voice translation-rule 1003 rule 1 /12../ /331552\0/
Lab Guide
71
! voice translation-profile pstn-in translate calling 1001 translate called 1000 ! voice translation-profile pstn-out translate calling 1003 ! voice-port 0/0/0:1 translation-profile incoming pstn-in voice-port 0/0/0:2 translation-profile outgoing pstn-out ! dial-peer voice 9 pots incoming called-number 33155212.. direct-inward-dial port 0/0/0:1 ! dial-peer voice 97 pots destination-pattern 9[2-9]...... port 0/0/0:2 forward-digits 7 ! dial-peer voice 910 pots destination-pattern 9[2-9]..[2-9]...... port 0/0/0:2 forward-digits 10 ! dial-peer voice 9110 pots destination-pattern 91[2-9]..[2-9]...... port 0/0/0:2 forward-digits 11 ! dial-peer voice 90110 pots destination-pattern 9011T port 0/0/0:2 prefix 011 ! dial-peer voice 911 pots destination-pattern 911
72
no digit-strip port 0/0/0:2 ! dial-peer voice 9911 pots destination-pattern 9911 port 0/0/0:2 prefix 911 ! dial-peer voice 411 pots destination-pattern 9411 forward-digits 3 port 0/0/0:2 ! dial-peer voice 611 pots destination-pattern 9611 forward-digits 3 port 0/0/0:2

Lab Guide
73
Lab 4-3 Answer Key: Configuring Path Selection

Hunt Group Configuration

! dial-peer voice 11031 pots destination-pattern 1109 port 0/2/0 ! dial-peer voice 11041 pots destination-pattern 1109 preference 1 port 0/2/1
Redundant Path Configuration: HQ to BR

!
voice translation-rule 1200 rule 1 /^812/ // ! voice translation-profile strip-sites translate called 1200 ! voice translation-rule 1300 rule 1 /^812/ /9133112/ ! voice translation-profile add-pstn translate called 1300 ! dial-peer voice 812 voip translation-profile outgoing strip-sites destination-pattern 81212.. session target ipv4:10.1.4.102
!
dial-peer voice 8121 voip translation-profile outgoing add-pstn destination-pattern 81212.. preference 1 port 0/0/0:23
74
TEHO Configuration (Pod 1 to Pod 2)

! dial-peer voice 332 voip destination-pattern 913325552001 session target ipv4:10.2.4.101
!
dial-peer voice 3321 pots destination-pattern 913325552001 preference 1 forward-digits 11 port 0/0/0:23

Lab Guide
75
Lab 4-4 Answer Key: Implementing Calling Privileges on Cisco IOS Gateways
COR Configuration
dial-peer cor custom name local name intl name ld name 911 name int ! dial-peer cor list lock-local member local ! dial-peer cor list lock-ld member ld ! dial-peer cor list lock-intl member intl ! dial-peer cor list lock-int member int ! dial-peer cor list lock-911 member 911 ! dial-peer cor list key-int member int ! dial-peer cor list key-local member local member 911 member int ! dial-peer cor list key-ld member local member ld member 911
member int ! dial-peer cor list key-intl member local member intl member ld member 911 member int ! dial-peer voice 1103 pots destination-pattern 1103 corlist incoming key-ld corlist outgoing lock-int port 0/0/0 ! dial-peer voice 1104 pots destination-pattern 1104 corlist incoming key-int corlist outgoing lock-int port 0/0/1 forward-digits 7 ! dial-peer voice 97 pots corlist outgoing lock-local destination-pattern 9[2-9]...... port 0/0/0:0 forward-digits 7 ! dial-peer voice 910 pots corlist outgoing lock-local destination-pattern 9[2-9]..[2-9]...... port 0/0/0:0 forward-digits 10 ! dial-peer voice 9110 pots corlist outgoing lock-ld destination-pattern 91[2-9]..[2-9]...... port 0/0/0:0 forward-digits 11 !

Lab Guide
77
dial-peer voice 9011 pots corlist outgoing lock-intl destination-pattern 9011T port 0/0/0:0 prefix 011 ! dial-peer voice 911 pots corlist outgoing lock-911 destination-pattern 911 port 0/0/0:0 forward-digits 3 ! dial-peer voice 9911 pots corlist outgoing lock-911 destination-pattern 9911 port 0/0/0:0 forward-digits 3 ! ephone-dn 1 dual-line
number 1001 description 13125551001 name HQ Phone1-1 corlist incoming ld ! ephone-dn 2 dual-line
number 1002 description 13125551002 name HQ Phone2-1 corlist incoming intl !
78
Lab 5-1 Answer Key: Configuring Basic Gatekeeper Functionality

Cisco IOS Configuration: Corp-GK (HQ-1)

gatekeeper zone local HQ cisco.com 10.1.250.101 zone local BR cisco.com enable-intrazone zone prefix HQ 1... zone prefix BR 2... gw-type-prefix 1#* default-technology bandwidth interzone default 384 no shutdown
Cisco IOS Gateway Configuration: HQ

interface Loopback0 description Pod1 HQ loopback interface ip address 10.1.250.101 255.255.255.255 h323-gateway voip interface h323-gateway voip h323-id GW-P1HQ h323-gateway voip tech-prefix 1# h323-gateway voip bind srcaddr 10.1.250.101 ! gateway ! dial-peer voice 1200 voip destination-pattern 12.. session target ras ! ! ephone-dn 1 dual-line
number 1001 no-reg ! ephone-dn 2 dual-line
number 1002 no-reg

Lab Guide
79
Cisco IOS Gateway Configuration: BR

interface Loopback0 description Pod1 BR loopback interface ip address 10.1.250.102 255.255.255.255 h323-gateway voip interface h323-gateway voip id BR ipaddr 10.1.250.101 h323-gateway voip h323-id GW-P1BR h323-gateway voip tech-prefix 1# h323-gateway voip bind srcaddr 10.1.250.102 ! dial-peer voice 1100 voip destination-pattern 11.. session target ras
80
Lab 5-2 Answer Key: Implementing Gatekeeper-Based CAC

Cisco IOS Configuration: Gatekeeper

gatekeeper bandwidth interzone zone HQ 128 bandwidth interzone zone BR 128 no shutdown

Lab Guide
81
Lab 6-1 Answer Key: Configuring a Cisco UBE

Cisco UBE Configuration

voice service voip allow-connections h323 to sip allow-connections sip to h323 ! voice translation-rule 9011 rule 1 /^9011/ // ! voice translation-profile sip-out translate called 9011 ! interface Loopback0 ip address 10.1.250.101 255.255.255.0 h323-gateway voip interface ! dial-peer voice 9011 voip translation-profile outgoing sip-out destination-pattern 9011T session protocol sipv2 session target ipv4: 10.2.250.101 codec g711ulaw ! dial-peer voice 9012 voip destination-pattern . incoming called-number 3315551... direct-inward-dial codec g711ulaw
82

Cvoice v60 Lab Guide

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Cvoice v60 Lab Guide

Încărcat de

Drepturi de autor:

Formate disponibile

CIPT1

Cisco Voice over IP

2008 Cisco Systems, Inc.

2008 Cisco Systems, Inc.

Cisco Voice over IP (CVOICE) v6.0

Cisco Voice over IP (CVOICE) v6.0

2008 Cisco Systems, Inc.

CVOICE 6.0 Lab Topology

Phone1-2 7941/61 2101 Phone2-2 7941/61 2102

PSTN BR-1 BR-2

Phone5-1 7941/61 1201

(7941/61 or PC with NetMeeting)

2008 Cisco Systems, Inc. All rights reserved.

The addressing of the classroom pods is described in the following tables.

Cisco Voice over IP (CVOICE) v6.0

2008 Cisco Systems, Inc.

Address Table for Odd-Numbered Classroom Pods

Device Name Headquarters Pod X Gateway

Serial 0/0/0 Serial 0/0/1 T1 01/0

PRI Framing: ESF Line code: B8ZS

VLAN198 VLANX02 VLANX03

Management VLAN HQX voice VLAN HQX data VLAN

Branch Pod X Gateway

Fa0/0.X05 Fa0/0.X06 Fa0/0.198

10.X.5.102 10.X.6.102 3.X.0.3

Branch Pod X Switch

Fa0/0. X03 Fa0/0.198

10. X.3.102 3.X.0.4

HQX data VLAN Allows Telnet to switch from PodX

2008 Cisco Systems, Inc.

X = Pod number 1, 3, or 5. Y = Even number pod in pod pair.

Address Table for Even-Numbered Classroom Pods

Device Name Headquarters Pod Y Gateway

Serial 0/0/0 Serial 0/0/1 T1 01/0

Branch Pod Y Switch

Y = Pod number 2, 4, or 6. X = Odd number pod in pod pair.

Cisco Voice over IP (CVOICE) v6.0

2008 Cisco Systems, Inc.

BRX PSTN Area code and exchange HQ BR

Dial Plan Conventions

2008 Cisco Systems, Inc.

Cisco Voice over IP (CVOICE) v6.0

2008 Cisco Systems, Inc.

Lab 2-1: Configuring Analog Voice Interfaces

Lab 2-1: Configuring Analog Voice Interfaces

Phone1-2 7941/61 2101 Phone2-2 7941/61 2102

PSTN BR-1 BR-2

Phone5-1 7941/61 1201

(7941/61 or PC with NetMeeting)

2008 Cisco Systems, Inc. All rights reserved.

Analog telephones RJ-11 cables

2008 Cisco Systems, Inc.

Task 1: Configure an Analog Voice Port

Cisco Voice over IP (CVOICE) v6.0

2008 Cisco Systems, Inc.

2008 Cisco Systems, Inc.

You have configured and verified analog voice port parameters.

Task 2: Verify Analog Port Settings

Your output should resemble this.

2008 Cisco Systems, Inc.

Lab 2-2: Configuring POTS Dial Peers

Lab 2-2: Configuring POTS Dial Peers

(7941/61 or PC with NetMeeting)