unlock iewb vo vol2.v3.00.lab8.tasks

CCIE Voice Lab Workbook Volume II Version 3.0 Lab 8

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

Internetwork Expert Voice Workbook Volume II

Lab 8 Difficulty Rating (10 highest): 9

Lab Overview:

This lab scenario is a mock lab exam designed to simulate the conditions of Cisco Systems’ CCIE Voice Lab exam. This lab should be completed within 8 hours. The only resource that should be used while configuring this lab is Cisco’s documentation set. This documentation is available in both DVD format, and online at http://www.cisco.com/go/support.

Lab Instructions:

Prior to starting, ensure that the initial configuration scripts for this lab have been applied. For a current copy of these scripts, see the Internetwork Expert members site at http://members.internetworkexpert.com. The initial configurations for all routers and switches include IP addressing and routing configuration.

Refer to the lab diagram available under your member’s account for information on the topology and IP addressing. In addition to the lab diagram, please download and reference the Table Reference Guide while completing the lab. Both the diagram and reference guide are available under the Voice Volume II section of your member’s account.

The lab could be completed using either soft-phones (e.g. Cisco IP Communicator or IP Blue’s VTGO) or by using Cisco 7960, 61, 62, and 65 IP phones. Refer to your rack rental user’s guide for detailed instructions on connecting the remote soft-phones to the rack.



Grading:

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

Point Values:

The point values for each section are as follows:

Section Point ValueInfrastructure Configuration 4Station Devices 8Trunks & Gateways 10Call Routing 15CAC & Codecs 3Media Resources 9Applications & Services 5High Availability 4QoS 4Voice Mail 14CUCCX 3Presence 4Total: 79



1. Infrastructure Configuration

1.1. VLAN Assignment

• Configure the on-site switches to support Cisco IP phones • Make sure you provided support for future PCs to be connected to the Cisco IP

Phones internal switch port

2 Points

1.2. DHCP

• Configure the routers at all three sites to allocate IP addresses via DHCP per the following requirements:

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

/24 subnet using the rack topology diagram as reference o Set the TFTP server’s IP to the Publisher CallManager’s IP address for

the HQ and BR1 devices

• Make sure you only allocate IP addresses with the last octet in range “60-90”

2 Points



2. Station Devices

2.1. CCM IP Phones

• Perform the following with the CallManager IP Phones

o Register the IP phones at the HQ and BR1 sites with the CallManager cluster

o Assign directory numbers to the IP Phones

• Use the following table as your reference to accomplish this task

Phone Extension DID NumberHQ IP Ph1 2001 7752011001HQ IP Ph2 2002 7752011002HQ IP Ph3 2003 7752011003BR1 IP Ph1 2001 3123012001BR1 IP Ph2 2002 3123012002

• Configure the IP Phones so that they use consistent calling names across the sites, so that you can distinguish a calling phone by name. An example of an acceptable name is “HQ IP Ph1”

• By the end of this task you should be able to place VoIP calls to/from all IP Phones and distinguish them by calling names/numbers

3 Points

2.2. CME IP Phones

• Register the IP phones at the BR2 location with the CallManager Express system running in R3

• Assign directory numbers to the IP Phones, create users and associate them with respective phones

• Use the following table as a reference for information needed to accomplish this task

• Unanswered calls should be forwarded to voicemail after 7 seconds

Phone Extension User DID NumberBR2 IP Ph1 3001 br2user1 21313001BR2 IP Ph2 3002 br2user2 21313002

3 Points



2.3. CME IP Phones Layout

• Configure the IP Phones so that they use meaningful calling names for their primary lines. Example of acceptable names are “BR2 Ph1” for BR2 IP Phone1

• Apply configuration to display the fully globalized phone number in the upper right corner of the header bar (+442321313XXX)

• Both Phones 1 and 2 should be able to pickup calls to number 3005, 3006, and 3007 on button 3 of the phone

3 Points

3. Trunks & Gateways

3.1. MGCP Gateway

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

• Use only the first 3 channels 3 Points

3.2. H.323 Trunk

• Configure the BR1 on-site router as an H.323 gateway and add it to the CallManager 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 Gateway

• Configure Br2 as a H.323 gateway to process calls for the local CUCME installation

• Use the first 5 timeslots of the E1 • Ensure ISDN Information Elements are sent outbound

3 Points



4. Call Routing

4.1. Route Plan Description

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

• Users should be able to dial “911” and “9911” to reach emergency services where 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 BR2 location • Long-distance (national) calls at the HQ and BR1 sites 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 the toll-alert code “00” and variable length number

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

0 Points

4.2. HQ Basic Call Routing

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

Call Type HQ PatternEmergency 911Local [2-9]XXXXXXNational/LD 1[2-9]XX[2-9]XXXXXXInternational 011 + Variable lengthToll-Free 1800XXXXXXX

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

o All calls from HQ should be routed using only one route pattern o All calls from HQ phones should make use of the Local Route Group

• All calls must have both the calling and called number type set according to the following values. In addition, the calling party number must correspond to each pattern listed for the corresponding type:

• Emergency/Local: Subscriber (Calling Party Number 7 Digits) • National: National (Calling Party Number 10 Digits) • International: International (Calling Party Number +11 Digits)

4 Points



4.3. BR1 Basic Call Routing

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

o The phones at the BR1 location should prefer the gateway at Br1 as the PSTN gateway

o Apply configuration to reach the BR2 on-site phones via abbreviated number dialing

o Callers attempting to reach 1900XXXXXXX patterns should hear the following message after dialing “Your call cannot be completed as dialed, please consult your directory and call again or, ask your operator for assistance…”

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

Call Type BR1 PatternEmergency 911Local [2-9]XXXXXXNational/LD 1[2-9]XX[2-9]XXXXXXInternational 011 + Variable length

4 Points

4.4. Inbound Localization

• Calls from PSTN numbers local to the HQ and BR1 sites should be handled as follows on the relevant sites phones:

o Inbound Display on phone: 7 Digits, ex. 5011111 o Secondary Number displayed in directories ex. +17755011111

4 Points

4.5. BR2 Call Routing

• Ensure no access restrictions apply to BR2 phones, every phone is allowed to call any PSTN number

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

o The IP Phones should use R3 as the only PSTN gateway o All calls must have called number type set according to the following

values: • Emergency/Local: Subscriber • National: National • International: International

• The IP Phones should present their calling names only when calling international patterns, all other patterns should not display a calling name, and their phone number should fully globalized (ex. +442321313001)

3 Points



5. CAC & Codecs

5.1. Codec Manipulation

• Ensure you use the G.711 codec for voice calls within each site, and use G.729 between the HQ and BR1 sites

• Allow a maximum of two G.729 calls between the HQ and Br1 sites

3 Points 6. Media Resources

6.1. Hardware Resources

• Configure hardware DSP resources per following requirements:

o Register the HQ on-site DSP resource as a conference bridge with the CallManager

o Register the BR1 on-site DSP resources as a transcoder with the CallManager cluster

i. Configure a maximum of three transcoding sessions

• Ensure that HQ and BR1 devices only use the BR1 transcoding resources

3 Points

6.2. Music On Hold

• Stream Music on Hold from the CallManager Publisher and Subscriber servers per the following requirements:

o Use G.711 as the codec to stream MoH for the HQ and BR1 devices and stream music using multicast delivery

3 Points

6.3. Hardware Resources CUCME

• Configure hardware DSP resources per following requirements:

o Register the Br2 on-site DSP resource as a transcoder with the local CUCME installation

o Ensure a maximum of 3 sessions

3 Points



7. Applications & Services

7.1. Single Number Reach

• HQ Phone 1 should be configured for Single Number Reach • The PSTN number 18005553333 should ring when anyone calls HQ Phone 1 • Ensure calls can be transferred to the PSTN number only when ringing • Calls should only be transferred to the remote destination during the following

periods: o Monday, Tuesday, Thursday, & Friday from 8:00AM to 6:00PM PST

5 Points

8. High Availability

8.1. Basic SRST

• Configure the BR1 router to provide SRST services for local phones. Users should be able to access the dial plan patterns they have access to in normal mode

• Phones displays should show “SRST now in service” • SRST server should provide outside dial tone when a user dials “9” • Ensure users can reach voicemail by pressing the messages button on their

phones • After 10 seconds, unanswered calls should be forwarded to voicemail • Calls to 3123012005 should be able to picked up by both Br1 Phones

4 Points

9. QoS

9.1. Packet Marking

• Enable MLS QoS on SW1 and SW2 • Configure switchports to trust the CoS marking assigned by IP phones and

ensure this marking translates correctly to a CoS value of CS3 • Appliance packets should have an explicit value of CoS 1 assigned to them • For IOS VoIP gateways, ensure the signaling uses the DSCP value of CS3

4 Points



10. Voice Mail

10.1. Unity VM Integration

• You are planning to deploy a centralized Voice Mail system for your sites using the Unity server installed at the HQ location

• Provide a configuration to 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

3 Points

10.2. Unity Subscribers

• Create three voice mailboxes: for HQ IP Phone 2, HQ IP Phone 3 and BR1 IP Phone 2

• Use the password value “12345” for every user and any names/aliases of your choice

• Make sure you can send voice-mails between HQ and BR1 Phones, and get MWI lights lit correctly

• The unanswered phone call or calls to a busy phone line on the respective phones should be redirected to the Voice Mail system

3 Points

10.3. Call Schedules

• Create a new Holiday on July 4th • The Weekday schedule should be modified, to cover the hours of 8AM to 6PM

2 Points



10.4. CUE Initialization

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

o Use the voice mail pilot number “3500” o Use MWI on and off numbers “3998....” and “3999....” o Create an administrator user named administrator with the

password value “cisco” o Use number “3555” for Administration via Telephone (AvT)

• Allow up to three concurrent VM sessions to the CUE system, for VoIP and PSTN callers simultaneously

• Run the Web-init setup wizard to make sure CUE users may access their voicemail profiles via the web

3 Points

10.5. CUE Subscribers

• Create voice mailboxes for BR2 IP Phone 1 and IP Phone 2, and make sure users can log in without listening to the CUE tutorial

• Use the password value of “cisco” and a PIN value of “12345” for all users • Apply configuration to reach the VM pilot number from the PSTN • Test your configuration by sending messages between two users and verifying

that the MWI light goes on

3 Points



11. CRS

11.1. IPCC Express Integration

• Apply configuration to integrate your existing IPCCX installation at the HQ location with the CallManager 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” o ICD Agent username/password: “icdagent/cisco”

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

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 using the Desk Phone Presence Application

o Ensure the CUPC client can also be switched to SoftPhone mode

4 Points

unlock iewb vo vol2.v3.00.lab8.tasks

Documents