unlock iewb vo vol2.v3.00.lab2.tasks.0.01

8/13/2019 Unlock IEWB VO VOL2.v3.00.Lab2.Tasks.0.01

1/13

CCIE Voice Lab Workbook Volume II Version 3.0 Lab 2

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

Internetwork ExpertVoice Workbook Volume II

Lab 2

Difficulty Rating (10 highest): 8

Lab Overview:

This lab scenario is a mock lab exam designed to simulate the conditions of CiscoSystems’ CCIE Voice Lab exam. This lab should be completed within 7.5 hours. The

only resource that should be used while configuring this lab is Cisco’s documentationset. This documentation is available in both DVD format, and online athttp://www.cisco.com/go/support.

Lab Instructions:

Prior to starting, ensure that the initial configuration scripts for this lab have beenapplied. Troubleshooting scenarios have been introduced into this lab. Ensure allscenarios are working before completing the lab.

Grading:

This practice lab consists of various sections totaling 79 points. A score of 59 points isrequired to achieve a passing score. A section must work 100% with the requirementsgiven in order to be awarded the points for that section. No partial credit is awarded. If asection has multiple possible solutions, choose the solution that best meets therequirements.


2/13



1. Infrastructure Configuration

1.1. VLAN Assignment

• Configure the on-site switches to support Cisco IP phones• Provide support for future PCs to be connected to the Cisco IP Phones internal

switch ports

1 Points

1.2. DHCP

•

Configure the routers at all sites to allocate IP addresses via DHCP per thefollowing requirements:

o Create three DHCP pools for voice VLANs in routers R1, R2 and R3o Configure the DHCP pools to allocate IP addresses from the respective

/24 subnet using the diagram for referenceo The Publisher is the TFTP server for IP Phones at HQ and BR1 siteso R3 is the TFTP server for IP Phones at BR2 site

• Configure the remaining DHCP settings as you find appropriate for other tasks

3 Points

2. Station Devices

2.1. CallManager IP Phones

• Using the following table as your reference, register the IP phones at HQ andBR1 locations with the CallManager cluster and assign directory numbers to theIP Phones

Phone Extension User DID Number

HQ IP Ph1 1001 7752011001

HQ IP Ph2 1002 7752011002

HQ IP Ph3 1003 icdagent 7752011003

• Refer to Task 2.3 for details on presentation setting to be configured for IPPhones

• By the end of this task you should be able to place VoIP calls between all IPPhones and distinguish them by calling numbers and names

3 Points


3/13



2.2. CME IP Phones

• Using the following table as your reference, register the IP phones at BR2location with the CME and assign directory numbers:

Phone Extension DID Number

BR2 IP Ph1 3001 21313001

BR2 IP Ph2 3002 21313002

• Refer to Task 2.3 for details on the presentation setting to be configured for IPPhones

• Ensure the configuration allows call-waiting functionality with primary lines. Anew incoming call should be displayed on the LCD of the called phone

• Only allow call-transfers to local IP Phone numbers

3 Points

2.3. Presentation Settings

• Configure the IP Phones so that they use consistent calling names across thesites, allowing the ability to distinguish a calling phone by name. An example ofan calling name is “HQ IP Ph1”

• IP Phones should present their full DID number and calling name (10 digits forthe HQ and BR1, and 8 digits for BR2) when calling external (PSTN) destinationsif not explicitly instructed to avoid this

1 Points


4/13



3. Trunks & Gateways

3.1. MGCP Gateway

•Register the digital gateway at the HQ location as an MGCP endpoint with theCallManager cluster

• Use only the first 3 channels2 Points

3.2. H.323 Trunk

• Configure the BR1 on-site router as an H.323 gateway and add it to theCallManager cluster

• Ensure the gateway uses the H.323 signaling method that does not try to

negotiate media parameters during the call establishment phase

3 Points

3.3. H.323 Gatekeeper

• Configure the HQ router as an H.323 gatekeeper, using the local zone name“ZONE_ 01”

• Configure BR2 to act as H.323 gateway per the following requirements:

o Configure BR2 ISDN E1 port settings and use gateway name “BR2_GW”o Ensure that the BR2 router uses it’s Loopback0 interface to interact with

the gatekeepero Make sure the BR2 router does not attempt to register it’s E.164 endpoints

with the gatekeeper

• Configure the CallManager cluster and BR2 router to register with the gatekeeperusing tech-prefix “1#”

3 Points

3.4. H.323 Gatekeeper

• Allow a call to route through the gatekeeper only if it matches one of theconfigured prefixes

• Since only one tech-prefix is in use, make sure a call initiated from the H.323gateway is not routed back to the same gateway

• Allow a call to route for zone prefix “1*” towards the CallManager cluster androute calls to prefix “44*” towards the BR2 router

• Ensure the Subscriber CallManager is used first to route a call towards theCallManager cluster

3 Points


5/13




6/13



4. Call Routing

4.1. Route Plan Description

• Phones at all locations use code “9” to access the PSTN. Outside dial toneshould be provided as soon as “9” has been dialed

• Users should be able to dial “911” and “9911” to reach emergency serviceswhere applicable

• Make sure “9” is stripped for calls going to PSTN• Local area PSTN calls are placed to 7-digit numbers at the HQ and BR1

locations, and to 8-digit numbers at the BR2 location• Long-distance (national) calls at the HQ and BR1 are placed to 10-digit numbers

using code “1” for toll-alert, and to 10 digit numbers at BR2 using code “0” for toll-alert

• International calls at the HQ and BR1 are signaled using access code “011”along with the variable length number

• International calls at BR2 are placed using toll-alert code “00” and variable lengthnumber

• Users may terminate their international numbers dialing using the “#” sign, inorder to place the call immediately, without waiting for the inter-digit timeout

0 Points

4.2. HQ Basic Call Routing

• Configure call routing for the HQ Phones per the following requirements:

o Route calls to the HQ local area numbers using the HQ gateway as theprimary and BR1 as secondary, in the case of the primary failing

o Long distance calls should also be placed using the HQ gateway asprimary and BR1 as secondary

o Use the on-site gateway only to place Emergency and International calls

• Use the following table as reference on dialing patterns for HQ site:

Call Type HQ PatternEmergency 911

Local [2-9]XXXXXX

National/LD 1[2-9]XX[2-9]XXXXXX

International 011 + Variable length

• Implement classes of restriction so that HQ IP Phone 2 is only allowed to callEmergency numbers and only HQ IP Phone 3 is allowed to call Internationalnumbers

3 Points


7/13



4.3. BR1 Basic Call Routing

• Configure call routing for BR1 phones per the following requirements:

o Use the following table as a reference on dialing pattern for the BR1 site

Call Type BR1 Pattern

Emergency 911

Local [2-9]XXXXXX

National/LD 1[2-9]XX[2-9]XXXXXXToll-Free 1800XXXXXXX

International 011 + Variable length

o The phones at the BR1 location are only allowed to use the on-site

gateway for all PSTN patternso The phones should be able to fall back to the HQ gateway as a backup

PSTN access point for local calls onlyo Require the input of FAC “001” to call Toll-Free numbers with

authorization level value of “5”

• Implement classes of restriction so that only BR1 IP Phone 2 is allowed to callInternational numbers

3 Points

4.4. Toll Bypass

• Provide toll-bypass for calls from the HQ phones per the following requirements :

o Calls from the HQ phones to the BR1 area code should first be placedusing the BR1 gateway and then HQ

o Calls from the HQ phones to BR2 area code should be first placed usingthe H.323 gatekeeper and use the HQ gateway as backup

o Calls from BR1 phones to the HQ area code should be first placed using

the HQ gateway and then using BR1 gateway as backup

• When a TEHO call is placed via backup gateway, change the calling number tomake the call look like it comes from the tail-end site

3 Points


8/13



4.5. BR2 Call Routing

• Use the following table as a reference on dialing patterns for the HQ site:

Call Type BR2 Pattern

Emergency 999Local [2-8]XXXXXXX

National/LD 0[2-8]XXXXXXXXXInternational 00 + Variable length

• Configure call routing for BR2 phones per the following requirements:

o The local IP Phones should use the local router as the only PSTNgateway

o Provide configuration for tail-end hop-off routing towards HQ and BR1area codes, so that international calls from BR2 to the mentioned areasare first attempted via the H.323 gatekeeper

o A failed hop-off should be re-routed as a regular international call

• The IP Phones should hide their calling names when dialing any local number

3 Points

4.6. Abbreviated Dialing

o Configure abbreviated dialing to “1XXX”, “2XXX” and “3XXX” numbers per thefollowing requirements:

o When a user at the HQ or BR1 locations dials “3XXX”, as a first routingoption, attempt to place the call via H.323 gatekeeper

o If the gatekeeper rejects the call due to some reason (e.g. insufficientbandwidth) reroute it as a PSTN international call

o When a user at the BR2 location dials “1XXX” or “2XXX” place the call viathe gatekeeper first, and in the case it fails, re-route as a PSTN

international call

• For the HQ and BR1 phones only permit PSTN fallback if the respective Class ofRestriction permits international calls

3 Points


9/13



5. CAC & Codecs

5.1. Codec Selection

• Use the G.711 codec within the HQ location, and use G.729 for calls within theBR1 location

• Use the G.729 codec for calls between the HQ and BR1, BR2 locations and alsobetween BR1 and BR2

• Make sure VAD is disabled explicitly where required

2 Points

5.2. Call Admission

• Configure CallManager locations-based admission control between the HQ andBR1 locations. Ensure VoIP calls coming in from the gatekeeper to BR1 phonesare subject to CAC control

• Use the H.323 gatekeeper CAC to perform call admission between theCallManager cluster and BR2 location

• Allow 3 concurrent G.729 calls between the CallManager cluster and BR2 andthe same number of calls between the HQ and BR1 locations

2 Points

6. Media Resources

6.1. Hardware Resources

• Allocate hardware DSP resources per the following requirements:

o Configure R1 and R2 to provide DSP resources for transcoding servicei. Maximum of 1 session on R1, 8 sessions on R2

o Configure R1 as a conference bridge resource

3 Points


10/13



6.2. Media Resources Allocation

• Devices at each site are only allowed to use their local transcoding resources• All the devices must have access to the conference bridge configured in the HQ

location• Configure fallback to software MTP and conference resources when no hardware

resources are available

3 Points

6.3. Music on Hold

• Configure the Publisher and Subscriber CallManagers to send Music on Hold

audio feeds• The CallManager Subscriber server should be used first and Publisher as a

fallback media streaming agent• Music should be sent using the G.711 format inside the HQ region and using

G.729 when streaming to BR1

3 Points

7. Applications & Services

7.1. B-ACD

• Integrate B-ACD script with the CallManager Express system per the followingrequirements:

o Associate the ACD application with PSTN DID number “2 Y3 Y3000”o Ensure there is no wait for user input on an incoming call, announce a

greeting and start hunting for available number immediatelyo Create a new hunt-group containing the primary lines of both on-site IP

Phones

• After waiting for maximum time (600 seconds) on queue, a call contact should beredirected to the group voice mailbox with extension number “3000”

3 Points


11/13



8. High Availability

8.1. SRST

• Configure the Br1 router to provide SRST services to on-site IP Phones• The IP Phones should rehome to the SRST router in the case that both

CallManager servers fail• Preserve the dialplan developed earlier in the Call Routing section• Allow up to three local ad-hoc conferences, and distribute calls to extension

number “2000” among the local IP Phones

3 Points

9. QoS

9.1. Frame-Relay Traffic Shaping

• Configure the routers connected to the Frame-Relay cloud to conform to theirprovisioned CIR values

• Use the following command output to obtain information on Frame-Relay PVCCIRs:

VORack01R1#show traffic-shape

Interface Se0/0/1:0.1 Access Target Byte Sustain Excess Interval Increment Adapt

VC List Rate Limit bits/int bits/int (ms) (bytes) Active

101 512000 640 5120 0 10 640 -

Interface Se0/0/1:0.2 Access Target Byte Sustain Excess Interval Increment Adapt

VC List Rate Limit bits/int bits/int (ms) (bytes) Active201 384000 480 3840 0 10 480 -

• Use FRTS legacy commands to configure traffic shaping

3 Points


12/13



10. Voice Mail

10.1. Unity VM Integration

• Integrate your Unity installation with the CallManager cluster per the following

requirements:

o Use the voice-mail pilot number “1500”o The voice-mail ports should be in range “1501-1502”o Use numbers “1998” and “1999” for MWI On and Off settings

• Configure the Unity server to resynchronize MWI lights status every day at9:00am

3 Points

10.2. Unity Features

• Create voice mailboxes for HQ IP Phone 3 and BR1 IP Phone 2. Use thepassword value “12345” and names “HQ IP Ph3”, “BR1 IP Ph2”

• Users should not have to change their password from this value• Ensure users do not hear the Self-Enrollment Dialog when calling the system

3 Points

10.3. CUE Initialization

• Configure the CallManager Express system for integration with Cisco UnityExpress voice-mail per the following requirements:

o Use the voice mail pilot number 3500o Use MWI on and off numbers “3998....” and “3999....”

• Register BR2’s DSP farm with the CallManger Express as a hardware transcoderto allow G.729 calls to the voicemail

2 Points

10.4. CUE Advanced

• Create two voice mailboxes in the CUE system, for extension numbers “3001”and “3002” respectively

• Apply configuration so that a message sent to the extension number “3000” isstored in a shared mailbox, accessible to both IP Phone 1 and IP Phone 2 usersfrom within their respective voice mailbox menus

• A user transferred to a voice mailbox should be able to press “0” to be redirectedback to the owner’s extension

2 Points


13/13



11. CRS

11.1. IPCC Express Integration

• Apply configuration to integrate your existing IPCCX installation with theCallManager cluster per the following requirements:

o JTAPI user name prefix/password: “jtapi/cisco”o RMCM user name prefix/password: “rmcm/cisco”o CTI port range: “1401-1402”o Default application script name: “icd.aef”o CTI RP DN: “1400”

• Configure HQ Phone 3 for ICD agent, and assign it to a call service queue.Subscribe the phone to the IP Phone agent service

• Make sure the default application works, by placing a call to number “1400”

3 Points

11.2. Custom ICD Script

• Modify the default ICD script per the requirements below:

o Apply configuration to pass a new parameter, named “QueueDepth” to thescript

o If the number of contacts, waiting on queue, is greater or equal than“QueueDepth”, silently discard all new incoming calls (overflow condition)

• The default value for the “QueueDepth” parameter should be “3”

3 Points

12. Presence

12.1. Presence Integration

• Integrate the Presence Server (177.1.10.50) with the CUCM Server

o Ensure that HQ User 1 can control their phone with the CUPC client usingthe Desk Phone Presence Application

4 Points

unlock iewb vo vol2.v3.00.lab2.tasks.0.01

Documents