Unlock IEWB VO VOL2.v3.00.Lab6.Solutionsguide

CCIE Voice Lab Workbook Volume II Version 3.0 Lab 6 Solutions

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

Task 1.1

SW1: vlan 11 name VOICE ! vlan 12 name DATA ! interface range FastEthernet 0/2 - 4 switchport mode access switchport voice vlan 11 switchport access vlan 12

R2: vlan database vlan 11 name VOICE vlan 12 name DATA exit ! interface range FastEthernet 0/1/0 - 1 switchport mode trunk switchport trunk allowed vlan 1,11,12,1002-1005 switchport voice vlan 11 switchport trunk native vlan 12

SW2: vlan 11 name RACK1_VOICE ! vlan 12 name RACK1_DATA ! interface range FastEthernet 0/1 - 2 switchport mode access switchport voice vlan 11 switchport access vlan 12



Task 1.2

R1: ip dhcp pool PHONES network 177.1.11.0 /24 option 150 ip 177.1.10.10 default-router 177.1.11.1 lease 0 0 15

! dns-server 177.1.11.1 ! ip dhcp excluded-address 177.1.11.1 177.1.11.49 ip dhcp excluded-address 177.1.11.101 177.1.11.254


! dns-server 177.2.11.1

ip dhcp excluded-address 177.2.11.1 177.2.11.49 ip dhcp excluded-address 177.2.11.101 177.2.11.254


! ip dhcp excluded-address 177.3.11.1 177.3.11.49 ip dhcp excluded-address 177.3.11.101 177.3.11.254

Task 1.3

Step 1: Configure R1 and R2 as DNS servers for local sites R1 & R2: ip dns server ! ip host CUCM7-PUB 177.1.10.10 ip host CUCM7-SUB 177.1.10.20 ip host UNITY7 177.1.10.30 ip host CUCM-CLUSTER 177.1.10.20 177.1.10.10 ip host CUPS7 177.1.10.50



Step 2: Modify the CallManager Enterprise Parameters to reflect names you have configured. The phones will try to resolve the hostnames with the DNS provided via DHCP, i.e. with the respective on-site router. Run the CUCMAdmin utility and navigate to System > Enterprise Parameters. Change all URLs to use the “CUCM-CLUSTER” hostname instead of the Publisher default name or IP address.

Step 3: Make sure server hostnames are in use, and not the IP addresses for the CCM physical servers. Navigate to System > Cisco Unified CM and change the names or IP addresses to “CUCM7-PUB” and “CUCM7-SUB” respectively for the Publisher and Subscriber.

Step 4: Proceed with creating the Cisco CallManager group. Navigate to System > Cisco Unified CM Group and select the “Default” group. Change the order of the CallManagers so that the Subscriber is placed first and rename the group to “CUCM_GROUP”.

Task 2.1

Step 1: Navigate to Route Plan > Class of Control > Partitions and click the Add a New Partition link. Add two new partitions named “PT_USA" and "PT_GLOBAL"

Next navigate to Route Plan > Class of Control > Calling Search Space and click the Add a New Calling Search Space link

Add a new CSS called “CSS_HQ_DEVICE” containing partition “PT_USA”. Copy the new CSS and rename it to “CSS_BR1_DEFAULT". Next, add a new CSS named "CSS_GLOBAL" adding partition "PT_GLOBAL"

Step 2: Navigate to System > Device Pool and click the Find button to list the available device pools. Rename the “Default” device pool to “DP_HQ”, and set the Calling Search Space for Auto-Registration to “CSS_HQ_DEVICE” then click the Update button. Copy the “DP_HQ” device pool and name the new one “DP_BR1”. Finally, create a device pool named "DP_BR2".



Step 3: Use the CUCM Serviceability Subsystem. Navigate to Tools > Service Activation. Choose the server corresponding to the CUCM Publisher first. Activate all the services except for the following: “Cisco Messaging Interface“,“Security Services“,“Cisco Certificate Authority Proxy Function“ and “Cisco WebDialer“. Activate the same set of services, with the exception of “Cisco TFTP Server“, in the Subscriber CallManager.



Step 4: Login to the CUCMAdmin utility and proceed to System > Cisco Unified CM. Enable Auto-Registration with the “CCM-PUB” CallManager using extension range “1001-1003”, and the external phone number mask “775201XXXX”

Navigate to System > Cisco Unified CM Group and change the order of the CallManagers in the group so that “CUCM-PUB” is preferred over “CUCM-SUB”. Don't forget to switch it back, after the auto-registration has completed. Phones will now auto-register.

Perform the following steps to complete the IP Phone registration & configuration.

Step 1: If you are using soft-phones, configure them to register with the CallManager server. Next, login to the CCMAdmin utility, navigate to Device > Phone and click the Find button to list all registered phones. Ensure all your IP phones have registered with the CallManager cluster.



Create a table of IP Phone MAC addresses and their associations to the IP Phones in the rack (e.g. MAC “0123.4567.89AB” is HQ IP Phone 1 etc). Use the “show cdp neighbor“ command on the switches to accomplish this. Using the MAC address table, locate the respective phone in the list of registered phones and start configuring them one by one.

Step 2: Select the phone you want to configure and set the proper “Device Pool” (“DP_HQ” or “DP_BR1”), “Description” (e.g. “HQ IP Ph1”), “Calling Search Space” (“CSS_HQ_DEFAULT” for the HQ Phones and “CSS_BR1_DEFAULT” for the BR1 Phones), at the device-level settings.

Step 3: Once you have finished with the device settings, click on the primary DN (Line 1) of the phone. Change the “Directory Number” to match the one assigned to the phone per the information provided. Set “Display (Internal Called ID) ” to a value that matches the phone, e.g. “HQ IP Ph1”. Ensure the “External Phone Number Mask” matches the site the phone belongs to (“775201XXXX” and “312301XXXX” for HQ and BR1 respectively).

Repeat Steps 2-3 until you have all the phones configured.

Tasks 2.2 - 2.3 R3: ! ! NTP master is needed to keep the local clock in “sync”! ntp master ! ! telephony-service max-ephones 2 max-dn 16 ip source-address 177.3.11.1 port 2000 dialplan-pattern 1 21313... extension 4 create cnf-files secondary-dialtone 9 date-format mm-dd-yy

time-format 12 system message CallManager Express at BR2 ! ephone-template 1 softkeys idle Redial Pickup CFwdAll

! ephone-dn 1 dual number 3001



name BR2 IP Ph1 description 21313001 label Manager 3001 call-forward busy 3555 call-forward noan 3555 timeout 12 ! ephone-dn 2 number 3011

! ephone-dn 3 dual number 3002 name BR2 IP Ph2 description 21313002 call-forward busy 3555 call-forward noan 3555 timeout 12 ! ephone-dn 4 number 3012 label Assistant 3012

! ! Assign mac-addresses per your topology! ephone 1 mac-address 0006.D7E5.C8E1 ephone-template 1 button 1:1 button 2:2 user br2user1 password cisco restart ! ephone 2 mac-address 000C.F12F.C447 ephone-template 1 button 1:3 button 2:4 user br2user2 password cisco restart



Task 3.1

Step 1: Locate the port. The location will be used to configure the T1 and gateway.

VORack01R1#show diag Slot 0:

C2811 Motherboard with 2FE and integrated VPN Port adapter, 2 ports Port adapter is analyzed Port adapter insertion time 6d13h ago Onboard VPN : v2.3.3 EEPROM contents at hardware discovery: <snip> WIC Slot 0: T1 (2 port) Multi-Flex Trunk WAN daughter card <snip>

From the output above, the location is determined to be 0/0 (Slot 0 of the router, Slot 0 of the motherboard)

Step 2:

R1:

! ! Define the isdn switch-type (In this case NI2) ! isdn switch-type primary-ni ! ! Enable clock participate ! network-clock-participate wic 0 ! ! Configure the controller, and ensure the PRI protocol is MGCP ! controller t1 0/0 framing esf linecode b8zs pri-group timeslots 1-3 service mgcp ! ! Bind the Layer 3 packets to the CUCM system ! interface serial 0/0/0:23 isdn bind-l3 ccm-manager ! ! Configure the MGCP settings, ensuring the call agent and redundant ! host are both configured



! ! mgcp mgcp call agent 177.1.10.20 mgcp bind control source loopback 0 mgcp bind media source loopback 0 mgcp dtmf voip codec all mode out-of-band ! ccm-manager redundant-host 177.1.10.10 ccm-manager mgcp ccm-manager switchback immediate !

Step 3:

On the CUCM Publisher server, navigate to Device > Gateway. Click the Add New button, and follow through the steps to configure the gateway:

After selecting the type (2811), select the protocol (MGCP)

Configure the gateway. Use the full hostname of R1 for the domain name. Select the NM-4VWIC-MBRD as the module in Slot 0, and NI2 for the switchtype:



Step 4:

Click save, then select the subunit where the card is located. This location was determined earlier (0/0/0):

Click save once again, then click the link for the T1 Card:



Chose the gateway protocol to be used, in this case PRI:

Configure the applicable settings for the gateway. The End-Point name and description are automatically configured, and will be used later for configuration of the channel status. All settings required must be configured as shown below:

Continue with further configuration of the gateway. The PRI Protocol Type is automatically set, however you must change the Channel Selection Order. Next, uncheck the Inhibit restarts at PRI initialization, and check the Enable status poll option boxes.



Also check the following three options, which will enable IE (information element) delivery and redirection:



Click the save button, and copy the End-Point Name.

Step 5:

Navigate to System > Service Parameters. Chose the Publisher server, and the Call Manager Service:

Once the page has loaded, click the Advanced button, which will display all of the advanced parameters:



Locate the Change B-Channel Maintenance Status 1 Field under the Clusterwide Parameters, and enter the endpoint name of the gateway followed by = 0001 1111 1111 1111 1111 1111. The field should appear like this:

S0/SU0/DS1-0@VORack01R1 = 0001 1111 1111 1111 1111 1111

Repeat the steps above to configure R2 as an MGCP gateway with the applicable settings for R2.



Task 3.2

Perform the following steps to configure CallManager and R3 for SIP VoIP signaling:

Step 1: R3: ! isdn switch-type primary-net5 ! controller E1 1/0 linecode hdb3 framing crc4 pri-group timeslots 1-3 ! interface Serial 1/0:15 isdn outgoing display-ie ! voice service voip sip bind control source-interface Loopback0 bind media source-interface Loopback0 ! Disable Early media to match the outputsip-ua disable-early-media 180

! dial-peer voice 1 pots incoming called-number . direct-inward-dial port 1/0:15

Step 2: Navigate to the Device > Trunk section of the menu. Click the Add a New Trunk link. Choose “SIP Trunk” for the “Trunk Type” and click the Next button. Configure the trunk settings per the following table:

Field ValueDevice Name “TRUNK_SIP_BR1”Device Pool “DP_HQ”Destination Address “177.1.254.3”Significant digits “4”Calling Search Space “CSS_HQ_DEVICE”Redirecting Number IE Delivery - Outbound

Check

Redirecting Number IE Delivery- Outbound

Check

Click the Insert button then click the Reset Trunk button.



Task 4.2

Step 1: Navigate to System > Service Parameters then select the CUCM service on the Publisher. Set the “Stop Routing on Unallocated Number Flag” field to “False”.

Step 2: Navigate to Call Routing > Route/Hunt > Route Group and click the Add a New Route Group link. Create the following route groups: “RG_HQ”, “RG_BR1” and “RG_BR2”, each corresponding to the appropriate Gateway/Trunk.

Step 3: Navigate to Call Routing > Route/Hunt > Route List. Click the add new button, and create a new Route List named RL_LOCAL:

Click save, then click the Add Route Group button. Select the “Standard Local Route Group”:



Step 4: Navigate to System > Device Pool. Select the DP_HQ. Set the Local Route Group to the corresponding route group. Repeat this step for the branch sites.

Step 1: Navigate to Call Routing > Route Hunt > Route Pattern. Create a new pattern \+! Ensure the Urgent Priority box is checked, and the Local Route Group is used:



Step 2: Navigate to Call Routing > Translation Pattern. Click Add New, and create the following Translation Patterns. Use the table below for reference:

Translation Pattern Partition/CSS & (Settings)9.1[2-9]XX[2-9]XXXXXX PT_USA / CSS_GLOBAL (Not Urgent)

Number Type: National / Plan: ISDNPrefix + (Called)Strip Predot (Discard Digits)

9.[2-9]XXXXXX PT_USA / CSS_GLOBAL (Not Urgent)Number Type: Subscriber / Plan: ISDNPrefix + (Called)Strip Predot

9.011! PT_USA / CSS_GLOBAL (Not Urgent)Number Type: International / Plan: ISDNPrefix + (Called)Strip Predot

911 PT_USA / CSS_GLOBAL (Urgent)Number Type: Subscriber / Plan: ISDNPrefix + (Called)Strip Predot

9.911 PT_USA / CSS_GLOBAL (Urgent)Number Type: Subscriber / Plan: ISDNPrefix + (Called)Strip Predot

9.1800XXXXXXX PT_USA / CSS_GLOBAL (Urgent)Number Type: Subscriber / Plan: ISDNNo Calling Party External Phone MaskStrip Predot

Step 3: Navigate to Call Routing > Transformation Pattern > Called Party Transformation Pattern. Click Add New, and create the following Transformation Pattern: \+.!



Step 4: Navigate to Device > Gateway. Select the MGCP Gateway for R1. Choose the Called and Calling Party Transformation CSSs:

Repeat this step on the Br1 gateway.

Step 5: Navigate to Device > Phone. Select each phone and set the relevant Device CSS:



Repeat this step for each phone using the appropriate sites CSS.

Task 4.4

Step 1: Create two additional route lists (note the use of Calling Number Masks to hide the original calling number):

Route List Route Group Digits Manipulation

RG_BR1

Strip PreDot +Use External Phone Mask=”On”

RL_HQ_TEHO_BR1_BAK_HQ(TEHO to the BR1 area code)

RG_HQ

Strip PreDot + Prefix Called: “1312”+Calling Number Mask: “1312301XXXX”

RG_HQ

Strip PreDot +Use External Phone Mask=”On”RL_BR1_TEHO_HQ_BAK_BR1

(TEHO to the HQ area code)

RG_BR1

Strip PreDot + Prefix Called: 1775+Calling Number Mask: “1775201XXXX”



Step 2: Create the following route patterns for Tail-end hop-off prefixes:

Pattern Partition Route List

91312.[2-9]XXXXXX PT_HQ_PSTN_DEFAULT RL_HQ_TEHO_BR1_BAK_HQ

91775.[2-9]XXXXXX(CLID Restricted)

PT_BR1_PSTN_DEFAULT RL_BR1_TEHO_HQ_BAK_BR1

Task 4.6

Step 1: Configure the PSTN dialplan:

R3: dial-peer voice 999 pots desc == Emergency port 1/0:15 destination-pattern 999 forward-digits 3

! dial-peer voice 900 pots description == Local numbers 8 digits destination-pattern 9[2-8].......$ port 1/0:15

! dial-peer voice 901 pots description == LD 10 digits destination-pattern 90[2-8].........$ port 1/0:15 prefix 0 ! dial-peer voice 902 pots description == International destination-pattern 900.T port 1/0:15 prefix 00



Step 2: Configure the TEHO dialing patterns:

R3: ! ! TEHO HQ ! dial-peer voice 90017750 voip description == TEHO HQ destination-pattern 9001775201....$ session protocol sipv2 session target ipv4:177.1.10.20 codec g711ulaw no vad preference 1 dtmf-relay rtp-nte ip qos dscp cs3 signaling ! dial-peer voice 90017751 voip description == TEHO HQ destination-pattern 9001775201....$ session protocol sipv2 session target ipv4:177.1.10.10 preference 2 codec g711ulaw no vad dtmf-relay rtp-nte ip qos dscp cs3 signaling

! ! TEHO BR1 ! dial-peer voice 90013120 voip description == TEHO BR1 destination-pattern 9001312301....$ session protocol sipv2 session target ipv4:177.1.10.20 codec g711ulaw no vad preference 1 dtmf-relay rtp-nte ip qos dscp cs3 signaling ! dial-peer voice 90013121 voip description == TEHO BR1 destination-pattern 9001312301....$ session protocol sipv2 session target ipv4:177.1.10.10 preference 2 codec g711ulaw no vad dtmf-relay rtp-nte ip qos dscp cs3 signaling



Step 3: PSTN backup for TEHO dialing patterns

R3: ! ! TEHO PSTN Backup ! dial-peer voice 90017752 pots description == TEHO HQ

destination-pattern 9001775201....$ prefix 001775201

port 1/0:15 preference 3 ! dial-peer voice 90013122 pots description == TEHO HQ destination-pattern 9001312301....$ prefix 001312301 port 1/0:15 preference 3

Step 4: To handle the incoming TEHO calls from BR2 to the CallManager cluster, create a new partition named “PT_SIP_TRUNK” along with a new CSS named “CSS_SIP_TRUNK” containing this new partition and the partition “PT_INTERNAL”. Assign the new CSS to device “TRUNK_BR2” under the Device > Trunk section of the menu.

Step 5: Add the following two route patterns to the new partition “PT_SIP_TRUNK”:

Pattern Partition Route List

9001775.XXXXXXX PT_SIP_TRUNK RL_HQ

9001312.XXXXXXX PT_SIP_TRUNK RL_BR1



Task 4.7 R3:ephone-dn 1 call-forward busy 3002 call-forward noan 3002 timeout 12 ! ephone-dn 3 call-forward busy 3012 call-forward noan 3012 timeout 12 call-forward max-length 0

! ephone-dn 4 call-forward busy *3001 call-forward noan *3001 timeout 12 call-forward max-length 0

ephone-dn 10 number *3... call-forward all 3500 description Redirect to VM

Task 5.1

Step 1: Navigate to System > Location and notice the Hub_None Location link. This will be used for the HQ Site phones. Click the Add New button, and create two locations corresponding to the remote sites and name the locations “LOC_BR1” and “LOC_BR2”. Set “LOC_BR1” bandwidth to 72Kbps (3x24Kbps) and “LOC_BR2” bandwidth to 48Kbps (2x48Kbps):

Step 2: Navigate to System > Region then click the Find button to list available regions. Rename the “Default” region to “REG_HQ”. Add three new regions “REG_BR1”, “REG_BR2”, “REG_MOH”. Configure the region codec settings per the following matrix:



HQ BR1 BR2 MOHHQ G.711 G.711 G.729 G.711BR1 G.711 G.729 G.711BR2 G.711 G.711MOH G.711

Modify the Region to Region codecs under the Relationship section of the page. Note that you must click the save button after setting each Regions relationship.

Step 3: Navigate to System > Device Pool and click the Find button to list all device pools in the system. For each of the device pools “DP_HQ”, “DP_BR1” and “DP_BR2” set the “Region” and “Location” to their respective settings:

Step 4: Navigate to Device > Gateway and click the Find button to list all gateways. For each of the devices (HQ, and BR1 gateway) depending on their site, set the “Location” field to “LOC_HQ”, “LOC_BR1”. Next, navigate to Device > Trunk and modify the LOC for the Trunk to Br2.



Task 6.1

Register R1’s DSP farm with the CallManager cluster as a conference bridge:

Step 1:

R1:voice-card 0 no dspfarm dsp service dspfarm ! sccp local Vlan 11 sccp ccm 177.1.10.10 identifier 1 sccp ccm 177.1.10.20 identifier 2 sccp ip precedence 3 sccp ! sccp ccm group 1 associate ccm 1 priority 2 associate ccm 2 priority 1 associate profile 1 register R1_CONF ! dspfarm profile 1 conference maximum-sessions 1 associate application SCCP no shut

Step 2: Navigate to Media Resource > Conference Bridge, then click Add a New Conference Bridge link. Set the “Conference Bridge Type” field value to “Cisco IOS Enhanced Conference Bridge”, “Name” to R1_CONF, “Device Pool” field value to “DP_HQ”, the “Location” field value to “HUB_NONE”, and “Security Mode” to Non Secure:



Register R2’s dsp-farm with the CallManager cluster as transcoders per the following instructions:

Step 1: R2:voice-card 0 no dspfarm dsp service dspfarm ! sccp local Vlan 11 sccp ccm 177.1.10.10 identifier 1 version 7 sccp ccm 177.1.10.20 identifier 2 version 7 sccp ip precedence 3 sccp ! sccp ccm group 1 associate ccm 1 priority 2 associate ccm 2 priority 1 associate profile 1 register R2_XCODER ! dspfarm profile 1 transcode codec g711ulaw codec g711alaw codec g729r8 codec g729ar8 maximum sessions 3 associate application SCCP no shut

Step 2:

Navigate to Media Resource > Transcoder. Click the Add a New Transcoder link. Set the “Transcoder Type” to “Cisco IOS Enhanced Media Termination Point”, set the “Device Name” to “R2_XCODER” and the “Device Pool” field to “DP_BR1”



Next, Organize media resources into Media Resource Groups (MRGs) and link the groups into Media Resource Group Lists (MRGLs) to be assigned to Device Pools.

Step 1: Navigate to Media Resource > Media Resource Group and create two MRGs each containing either the Publisher or Subscriber MoH servers. Check the “Use Multicast for MOH Audio” box for each of the groups, and name the groups as “MRG_MOH_PUB_MCAST” and “MRG_MOH_SUB_MCAST”

Create an MRG for the BR1 transcoder and name the group “MRG_XCODER_BR1”.

Create a MRG for the HQ hardware conference bridge, named “MRG_CFB_HW”.

Leave the remaining software resources in the default (null) media resource group, available to any device in the system.



Step 2: Create three MRGLs. One for each site: “MRGL_HQ”, “MRGL_BR1” and “MRGL_BR2” per the following table:

MRGL Name MRG List

MRGL_HQ

MRG_XCODER_BR1MRG_CFB_HWMRG_MOH_SUB_MCASTMRG_MOH_PUB_MCAST

MRGL_BR1


MRGL_BR2


Navigate to Media Resource > Media Resource Group List to accomplish this task:



Step 3: Navigate to System > Device Pool and change the “Media Resource Group List” for each device pool, assigning the MRGLs to the appropriate devices pools for each site.

Tasks 6.2 - 6.3

Step 1: Run the CCMAdmin utility and navigate to Service > Media Resource > Music on Hold Server. Locate the server corresponding to the Subscriber CallManager. Check the “Enable Multicast Audio Sources” on this MOH Server field.

Set the Base Multicast IP Address to “239.1.1.1” and port to “16384”. Choose ”Increment Multicast on IP Address”, and then click the Update button.

Step 2: Navigate to Service > Media Resource > Music on Hold Audio Source. Click the ”MOH Audio Source 1”, check the ”Allow Multicasting” field and then click the Update button.

Step 3: Navigate to Service > Media Resource > Music on Hold Server section of the menu. Locate the server corresponding to the Subscriber CallManager. Set the field ”Max Hops” corresponding to ”Multicast Audio Source 1” to “1” (so that multicast from the CallManager servers wont be able to reach site BR1)

Step 4: Create two MRGs under the Service > Media Resource > Media Resource Groupsection of the menu containing the Publisher and Subscriber MoH servers, name them “MRG_MOH_PUB” and “MRG_MOH_SUB”. Do not enable the multicast flag for any of these groups.

Step 5: Add an MRG named “MRG_MOH_SUB_MCAST” that contains only the Subscriber MoH server and has the multicast flag checked.

Step 6: Configure multicast routing on R1 and R2 as follows:

R1: ip multicast-routing ! interface FastEthernet 0/0.10 ip pim dense-mode !



interface FastEthernet 0/0.11 ip pim dense-mode ! interface Serial 0/0/1:0.1 ip pim dense-mode

R2: ip multicast-routing ! no ip igmp snooping ! interface Vlan 11 ip pim dense-mode ! interface Serial 0/0/1:0.1 ip pim dense-mode ! interface Loopback 0 ip pim dense-mode

Step 7: Replace the Multicast flow from the HQ site with a local multicast feed:

R2: ! call-manager-fallback moh music-on-hold.au multicast moh 239.1.1.1 port 16384 route 177.3.11.1 177.1.254.2 !

Task 7.1 R3: voice translation-rule 2 Rule 1 /1775201$....$/ /9001775201\1/ Rule 2 /13122301$....$/ /9001312301\1/ Rule 3 /^$.........$$/ /9\1/ ! voice translation-profile PREPEND_TO_CALLING translate calling 1 ! dial-peer voice 999 translation-profile incoming PREPEND_TO_CALLING incoming called-number . direct-inward-dial

port 1/0:15



Task 7.2 R3: dial-peer cor custom name PAGING-DN name REGULAR ! dial-peer cor list CSS-PAGING member PAGING-DN ! dial-peer cor list CSS-REGULAR member REGULAR ! dial-peer cor list PT-PAGING member PAGING-DN ephone-dn 14 number A888 paging ip 239.1.1.1 port 16384 corlist outgoing PT-PAGING ! ephone-dn 1 corlist incoming CSS-REGULAR ! ephone-dn 2 corlist incoming CSS-REGULAR ! ephone-dn 3 corlist incoming CSS-PAGING ! ephone-dn 4 corlist incoming CSS-PAGING

ephone 1 paging-dn 14

ephone 2 speed-dial 1 A888 label "Paging" paging-dn 14



Task 8.1

Step 1: Perform the following steps in order to enable SRST functionality:

Step 1: System > SRST. Click Add New, and enter a name and the Loopback IP of R2:

Step 2: System > Device Pool. Locate DP_BR1 and set the SRST Reference:

Step 3: Configure R2 to handle the incoming PSTN calls for BR1 IP Phones

R2: ! ! Translation-profile to trim DID numbers! voice translation-rule 1 Rule 1 /312301$....$$/ /\1/ ! voice translation-profile DID translate called 1



Step 4: Configure outgoing call handling for SRST using the dialing prefixes table for reference.

R2: ! SRST Dial-Plan ! dial-peer voice 1 pots incoming called . direct-inward port 0/0/0:23

translation-profile incoming DID ! dial-peer voice 911 pots destination-pattern 911 port 0/0/0:23 forward 3! dial-peer voice 9911 pots destination-pattern 9911 port 0/0/0:23 forward 3 ! dial-peer voice 900 pots desc == Local destination-pattern 9[2-9]......$ port 0/0/0:23

dial-peer voice 901 pots desc == LD destination-pattern 91[2-9]..[2-9]......$ port 0/0/0:23 prefix 1 ! ! ! dial-peer voice 902 pots desc == Toll-Free destination-pattern 91800.......$ port 0/0/0:23 prefix 1800 clid strip clid strip name ! dial-peer voice 903 pots desc == Intl destination-pattern 9011.T port 0/0/0:23 prefix 011 ! dial-peer voice 2000 pots destination-pattern 82...$ port 0/0/0:23 forward-digits 4 prefix 775201 !



dial-peer voice 3000 pots destination-pattern 3...$ port 0/0/0:23

forward-digits 4 prefix 01144232131

R2: ! ! Configure fallback from MGCP application! call application alternate default ccm-manager fallback-mgcp ! call-manager-fallback max-ephone 2 secondary-dialtone 9 max-dn 8 ip source-address 177.2.11.1 system message primary SRST services at BR1

call-forward pattern .T transfer-pattern .T transfer-system full-consult



Task 9.1 R1: ! ! map-classes for FR shaping ! map-class frame-relay SHAPE_BR1 frame-relay cir 512000 frame-relay mincir 512000 frame-relay bc 5120 frame-relay be 0 ! map-class frame-relay SHAPE_BR2 frame-relay cir 384000 frame-relay mincir 384000 frame-relay bc 3840 frame-relay be 0 ! interface Serial 0/0/1:0 frame-relay traffic-shaping

! interface Serial 0/0/1:0.1 no ip address

class SHAPE_BR1 interface Serial 0/0/1:0.2 no ip address

class SHAPE_BR2 ! router ospf 1 no passive-interface Virtual-Template 1 no passive-interface Virtual-Template 2

R2: map-class frame-relay SHAPE_HQ frame-relay cir 512000 frame-relay mincir 512000 frame-relay bc 5120 frame-relay be 0! interface Serial 0/0/1:0 frame-relay traffic-shaping

! interface Serial 0/0/1:0.1 no ip address no frame-relay interface-dlci 101 frame-relay interface-dlci 101 ppp virtual-template 1

class SHAPE_HQ ! router ospf 1 no passive-interface Virtual-Template 1



R3: map-class frame-relay SHAPE_HQ frame-relay cir 384000 frame-relay mincir 384000 frame-relay bc 3840 frame-relay be 0 !! interface Serial 1/1:0 frame-relay traffic-shaping

! interface Serial 1/1:0.1 no ip address no frame-relay interface-dlci 201 frame-relay interface-dlci 201 ppp virtual-template 1

class SHAPE_HQ ! router ospf 1 no passive-interface Virtual-Template 1



Tasks 10.1 - 10.3

Perform the following steps to integrate the Cisco Unity system with the CallManager

Step 1: Navigate to Voice Mail > Cisco Voice Mail Port Wizard. Follow through the configuration steps as shown below. Use the Navigation buttons at the bottom of the page to move between the configuration steps:

Set the number of ports to 2:

Use HQ related parameters for the Unity Call Routing configurations:



Next, Select the option to add the numbers to a new Line Group:



Use the default Line Group name:

Finally, review the settings on the confirmation page, and click Finish. The summary page will now display, and should appear as shown below:



Step 2: Click the Hunt List link from the Summary Page:

Click the Add New button. Name the Hunt List HL_VM, and check both options boxes:

Click the Save button, then click the Add Line Group button that will appear. Select the previously created Line Group, and click Save:



Step 3: Navigate to Voice Mail > Voice Mail Port Wizard. Click the link for the Hunt Pilot, and click the Add New button. Configure the Hunt Pilot as shown below:

Step 4: Navigate to Voice Mail > Voice Mail Pilot. Click the Add New button, and configure the settings for the Pilot: (# 1500, CSS_HQ, Check the Default Box)



Step 5: Navigate to Voice Mail > Message Waiting. Click the Add New button, and configure the two MWI numbers, one at a time. Use the copy button after the first configuration:

Step 6: Navigate to Voice Mail > Voice Mail Profile. Click the Find button, and select the Default Profile. Add the Pilot, and Mask to the configuration:



Step 7: Navigate to Cisco Unity Connections (177.1.10.30) Open the Cisco Unified Serviceability subsystem, navigate to Tools > Service Activation. Select all services, and click save:

Step 8: Open the Cisco Unity Connection Administration subsytem, and navigate to Telephony Integrations > Port Group. Click the Add New button, and configure the Port Group

Set the Display name to any value such as VM, and use the Port Name prefix created by the CUCM cluster for the Device Name Prefix: CiscoUM1-VI

**Do not include the 1 or 2 after the prefix name from the port numbers, this will not work properly, and the Unity server will never register with the CUCM

Set the IP Address to the Publishers IP



Step 9: Navigate to Telephony Integrations > Port. Click the Add New button, and configure the new ports:

Step 10: Navigate to Telephony Integrations > Port Group. From the Edit menu, select Servers:



Click the Add button, and enter the IP address of the Subscriber call Manager to both the CUCM servers, and TFTP servers. Ensure the order the CUCM servers is set as 0: SUB for CUCM servers, and 1: SUB for the TFTP servers. (This is the same logic used in the CUCM Group CM order):

Step 11: From the Edit menu, select Port Group Basics. Notice the Reset Required Message, and click the Reset button:



Task 10.2

Step 1: Navigate to System Settings > Authentication Rules. Uncheck the “Check against trivial passwords for extra security“ field and check the “Never Expires“ field then click Save:

Step 2: Navigate to Templates > User Templates. Selec the "voicemailusertemplate". Uncheck the “Set for Self-enrollment at Next Login" field then click Save:



Step 3: Navigate to Edit > Password Settings. Uncheck “User Must Change at Next Login":

Step 4: Navigate to Edit > Change Password. Set the password to 123456:



Step 5: Navigate to Users > Users. Click User > New User:

Use the table below to enter the User Information:

**Repeat this step to configure the remaining users.

Field ValueFirst Name “HQ”Last Name “IP Ph1”Display Name “HQ IP Ph1”Extension “1001”Alias “HQ IP Ph1”



Step 6: On the CUCM Server, Navigate to Device > Phone. Click the DN configuration link, and set the Forward to Voice Mail for the Busy and No Answer check boxes:

Configuration is now complete. Test by placing calls to applicable phones, and ensuring the MWI light comes on. Finally, use the messages button to reach the Unity Voicemail system, and check the message on the phone.



Tasks 10.4 - 10.5 R3: voice service voip allow-connection sip to sip ! telephony-service call-forward pattern .T transfer-pattern .T voicemail 3500 web admin system name administrator password cisco

dn-webedit time-webedit ! ip http server ip http path flash:/gui ! ! interface Service-Engine 0/0 ip unnumbered FastEthernet 0/0.11 service-module ip address 177.3.11.254 255.255.255.0 service-module ip default-gateway 177.3.11.1 no shutdown

ip route 177.3.11.254 255.255.255.255 Service-Engine 0/0

! ! Translation profile to simulate Voice-Mail mask! voice translation-rule 1 Rule 1 /.*$....$$/ /\1/ ! voice translation-profile TO_VOICEMAIL translate calling 1 translate called 1 translate redirect 1 ! ! Abbreviated numbers to access VM pilot and AvT! num-exp 3500 21313500 num-exp 3555 21313555

! ! DID number to access Voicemail! dial-peer voice 21313500 voip destination-pattern 21313500 session protocol sipv2 session target ipv4:177.3.11.254 dtmf-relay sip-notify codec g711ulaw max-conn 3 translation-profile outgoing TO_VOICEMAIL



! ! DID number to access AvT ! dial-peer voice 21313555 voip destination-pattern 21313555 session protocol sipv2 session target ipv4:177.3.11.254 dtmf-relay sip-notify codec g711ulaw max-conn 3 translation-profile outgoing TO_VOICEMAIL

! ! ephone-dn 15 number 3998.... mwi on ! ephone-dn 16 number 3999.... mwi off

CUE CLI:

Rack1R3#service-module Service-Engine 0/0 session Trying 177.3.11.1, 2025 ... Open CUE> CUE> en Password: CUE# offline !!!WARNING!!!: If you are going offline to do a backup, it is recommended that you save the current running configuration using the 'write' command, prior to going to the offline state.

Are you sure you want to go offline[n]? : y

CUE(offline)# restore factory default !!!WARNING!!!: This operation will cause all configuration and data on the system to be erased. This operation is not reversible.

Do you wish to continue[n]? : y Restoring the system. Please wait .....done System will be restored to factory default when it reloads.

Press any key to reload:

<output omitted>



IMPORTANT:: IMPORTANT:: Welcome to Cisco Systems Service Engine IMPORTANT:: post installation configuration tool. IMPORTANT:: IMPORTANT:: This is a one time process which will guide IMPORTANT:: you through initial setup of your Service Engine. IMPORTANT:: Once run, this process will have configured IMPORTANT:: the system for your location. IMPORTANT:: IMPORTANT:: If you do not wish to continue, the system will be halted IMPORTANT:: so it can be safely removed from the router. IMPORTANT::

Do you wish to start configuration now (y,n)? y Are you sure (y,n)? y

Enter Hostname (my-hostname, or enter to use se-177-3-11-254): CUE

Enter Domain Name (mydomain.com, or enter to use localdomain): cisco.com

IMPORTANT:: DNS Configuration: IMPORTANT:: IMPORTANT:: This allows the entry of hostnames, for example foo.cisco.com, instead IMPORTANT:: of IP addresses like 1.100.10.205 for servers used by CUE. In order IMPORTANT:: to configure DNS you must know the IP address of at least one of your IMPORTANT:: DNS Servers.

Would you like to use DNS for CUE (y,n)?n

WARNING: If DNS is not used CUE will require the use WARNING: of IP addresses.

Are you sure (y,n)? y

Enter IP Address of the Primary NTP Server (IP address, or enter for 177.3.11.1): 177.3.11.1

Enter IP Address of the Secondary NTP Server (IP address, or enter to bypass):

Please identify a location so that time zone rules can be set correctly. Please select a continent or ocean. 1) Africa 4) Arctic Ocean 7) Australia 10) Pacific Ocean 2) Americas 5) Asia 8) Europe 3) Antarctica 6) Atlantic Ocean 9) Indian Ocean #? 8



Please select a country. 1) Albania 16) Greece 31) Portugal

2) Andorra 17) Hungary 32) Romania 3) Austria 18) Ireland 33) Russia 4) Belarus 19) Italy 34) San Marino 5) Belgium 20) Latvia 35) Slovakia 6) Bosnia & Herzegovina 21) Liechtenstein 36) Slovenia 7) Britain (UK) 22) Lithuania 37) Spain 8) Bulgaria 23) Luxembourg 38) Sweden 9) Czech Republic 24) Macedonia 39) Switzerland 10) Denmark 25) Malta 40) Turkey 11) Estonia 26) Moldova 41) Ukraine 12) Finland 27) Monaco 42) Vatican City 13) France 28) Netherlands 43) Yugoslavia 14) Germany 29) Norway 15) Gibraltar 30) Poland #? 7

The following information has been given:

Britain (UK) Great Britain

Therefore TZ='Europe/London' will be used. Local time is now: Sat Nov 24 14:10:01 GMT 2007. Universal Time is now: Sat Nov 24 14:10:01 UTC 2007. Is the above information OK? 1) Yes 2) No

<output omitted>

IMPORTANT:: IMPORTANT:: Administrator Account Creation IMPORTANT:: IMPORTANT:: Create an administrator account. With this account, IMPORTANT:: you can log in to the Cisco Unity Express GUI and IMPORTANT:: run the initialization wizard. IMPORTANT::

Enter administrator user ID: (user ID): administrator Enter password for : administrator (password): cisco Confirm password for by reentering it: (password): cisco



Perform the following steps to complete Web-Initialization of Cisco Unity Express

Step 1: Run the CUE Web-Init dialog (CUCME system must be pre-configured already with the HTTP server enabled). Open the URL “http://177.3.1.254/Web” in your browser then login with the username “administrator” and the password “cisco”. Click the link Run Initialization Wizard.

Step 2: On the CallManager Express Login page enter hostname “177.3.11.1” (IP Address of the CUCME system) and the login/password you configured under “telephony-service” earlier (“administrator/cisco”).

Step 3: On the Import CUCME Users page, check that both users are already created in the CME system and that you checked the “Mailbox” fields.

Step 4: On the Defaults page, check “Blank password” and “Blank PIN” fields. On the Call Handling page set “Voice Mail Number” to “3500”, set AvT number as “3555”, then select “MWI On Number” as “3998….” and “MWI Off Number” as “3999….”. Finish the WebInit process.

Step 5: Go back to the CUE CLI prompt, and apply the following configurations, to create users and voice mailboxes:

CUE CLI: username br2user1 pin 12345 username br2user2 pin 12345 username pstnuser pin 12345 ! conf t ! username br2user1 phonenumber 3001 username br2user2 phonenumber 3002 username pstnuser phonenumber 999 ! groupname Broadcasters member pstnuser ! voicemail mailbox owner "br2user1" no tutorial end mailbox ! voicemail mailbox owner "br2user2" no tutorial end



Task 11.1

Perform the following configuration steps to configure the JTAPI subsystem:

Step 1: Login to the CUCCX machine using the following information:

Field ValueIP Address “177.1.10.40”Username (Windows) AdministratorPassword (Windows) ccieciscoUsername (CUCCX Initilization) AdministratorPassword (CUCCX Initilization) ciscociscoJTAPI Username/Password jtapi/ciscoRMCM Username/Password rmcm/cisco

Launch the CUCCX adminsitration using the Application Administration Internet Explorer shortcut on the desktop. Login using the credentials shown above

Choose Single Node, and click Setup:



Enter the CUCM Publisher information, and username/password (admin/cciecisco)

Select the license file from the Desktop:

Once, the license file has been verified, click Next, and wait the activation process to complete (which may take up to 10 minutes)



Add the Subscriber to the Selected AXL Service Providers: (Publisher first in order)

Add the Subscriber to the Selected CTI Managers: (Subscriber first in order)

Add the Subscriber to the Selected CTI Managers: (Subscriber first in order)



Set the following System Parameters:

Choose the language:

Click search to find the users from CUCCM. Move the CUCCX user to the Adminsitrator list, and ensure hquser3 is listed as a user:



The installation is now complete. Any JTAPI errors can be ignored, as they will be resolved later. Close the browser, then open it once again, and login with the cuccxadmin user. Step 2: Navigate to Subsystems > Cisco Unified CM Telephony. Click the Add a New Cisco Unified CM Telephony Call Control Group link. Fill in the fields using the table below:

Field ValueNumber of CTI Ports “2”Starting Directory Numbers “1401”Device Name Prefix “CTI”Device Pool “DP_HQ”Location “LOC_HQ”AAR Group “AAR_HQ”External Phone Number Mask “775201XXXX”Display “CTI Ports”

Click the Add button.

Perform the following steps to configure the CallManager system: Step 1: Navigate to User > Application User. Find the user name “rmcm”. Select the device corresponding to the HQ IP Phone 3. Check the “No Primary Extension“ and “No ICD Extension“ fields then click the Update button. Repeat this step to associate the “rmcm” user with BR1 IP Phone 2. Step 2: Ensure the user “hquser3” is in the corporate directory under User > End User. In addition, assign the IPCC extension to 1003:

Step 3:



Navigate to Device > Device Settings > IP Phone Services and click the Add a New IP Phone Service link.

Enter the “Service Name” as “IPPA” and the “Service URL“ as:http://177.1.10.40:6293/ipphone/jsp/sciphonexml/IPAgentLogin.jsp

(You may find this URL under “Cisco CAD Installation Guide” on the Cisco DocCD)

Click the link to Add a new Parameter and enter the following Parameters: Ext, ID, PWD:



Step 4: Navigate to the Device > Phone section of the menu and locate HQ IP Phone 3. On the Phone Configuration page click the Subscribe/Unsubscribe services Related links, then choose “IPPA” from the drop-down list click Continue and then click Subscribe.

Perform the following steps to configure the RMCM subsystem and create a JTAPI trigger: Step 1: Run the CRS Application Administration utility and then navigate to Subsystems > RMCM > Resource Groups. Click the Add a New Resource Group list link and set the ”Resource Group List Name” to “RG_DEFAULT” then click the Add button:

Step 2: Navigate to the Resources section and click on the “hquser3“. Change the “Resource Group” field to “RG_DEFAULT” then click the Update button.

Step 3: Click the Contact Service Queues link then click the Add a New Contact Queue link. Set “Contact Service Queue Name” to “CSQ_DEFAULT” and set the “Resource Pool Selection



Model” to “Resource Group” Click the Next button, then choose the “Resource Group” “RG_DEFAULT” and click the Add button.

Step 4: Navigate to Application > Application Management then click the Add a New Application link. Set “Application Type“ to “Cisco Script Application” and click the Nextbutton.

Step 5: Set the “Name“ field to “ICD”, “Maximum Number of Sessions“ to “2”, and the “Script“ field to “icd.aef”.Click the “CSQ” parameter check-box and set the parameter value to “CSQ_DEFAULT” and then click the Add button:



Step 6: Click the Add a New Trigger link set “Trigger Type” to “CM Telephony” and set the trigger parameters according to the following table:

Field ValueDirectory Number “1400”Maximum Number of Sessions “Default”Call Control Group “JTAPI Group #0”Device Pool “DP_HQ”Location “HUB_NONE”External Phone Number Mask “775201XXXX”Display “ICD Port”

Click the Add button.

Step 7: Navigate to System > Control Center then click the name corresponding to your server. Select the “CUCCX Engine” application and the click the Restart button.



Task 11.2

Step 1: Create a new user named “telecaster“ in the Global directory (User Management > End User), assign the password value of “telecaster” and a PIN value of “1234”. Check the “Enable CTI Application Use” field for this user. Click the Device Associations link and associate this user with “HQ IP Phone 3” as well. Do not select a primary or ICD extension for this user.

Step 2: Run the CRS Editor application, open the default script “icd.aef” and save it in the Default repository under the name “my_icd.aef”. Add a new “String” variable named “strScriptName” with the value of “Custom_ICD_Script”

Step 3: Add a new Expanded Call Variable to pass the script name to the ICD agent application. Navigate to Settings > Expanded Call Variables from the menu and in the Edit Expanded Call Variable window add a new variable with a “Name” value of “strScriptName”, “Type” of “Scalar” and “Description” field set to “Script Name”.

Step 4: Add a new “Enterprise::SetEnterpriseCallInfo” step right after the “Accept” step in the ICD script. Under the step properties, Select the “Expanded Call Variable” tab and click the Addbutton. Add a new variable with the “Value” of “strScriptName” and “Name” of “--strScriptName--”

Step 5: Enable MoH to be played to contacts waiting on queue. Add “Call Contact::Call Hold” and “Call Contact::Call Unhold” steps to the script, before and after the “Delay” step under the “Queued” branch of the “Select Resource” step.:

Step 6: Change the Agent Desktop layout and add a new field corresponding to your previously created Extended Call Variable to the field list. Start the Desktop Administration application from the “Cisco” menu. From the “Locations” list expand your cluster (e.g. “ccie”) and expand the “Enterprise Data Configuration” branch. Select “Enterprise Data” and under the “Field List” click the “Add” button and add a new field with the “Field Index” of “1” and “Field Name” of “strScriptName” and “Display Name” of “Script Name”.



Step 7: Edit the “default” layout, and add the new field to it and ensure that “strScriptName” is under the “Fields in Layout” section (move it from the “Available Fields” if needed). Click the Apply button and save changes to the “default” layout.

Step 8: Configure the IP Agent Phone service for single touch sign-on. Open the URL for IP Agent Phone Service (you may find it back in the IPCC integration section or copy and paste from Cisco IP Phone Services Configuration section) in your browser. Copy the URL “http://177.1.10.10:6293/ipphone/jsp/sciphonexml/IPAgentLogin.jsp” from the XML page and create a new IP Phone service named “IPPA Single Touch” under Device > Device Settings > Phone Services section.

Step 9: Add three new parameters named “ID”, “Pwd” and “Ext” to the new IP Phone service.These are to be used as automatic supplements of username, password and extension number for an ICD agent user.

Step 10: Navigate to the Device > Phone section of the menu and select “HQ IP Phone 3”. Click the Subscribe/Unsubscribe Services link and add the above-created service “IPPA Single Touch”. Set the parameter values as the following: “ID”=”icdagent”, “Pwd”=”cisco”, “Ext”=”2003”. Update the subscription to complete the task.

Unlock IEWB VO VOL2.v3.00.Lab6.Solutionsguide

Documents

Transcript of Unlock IEWB VO VOL2.v3.00.Lab6.Solutionsguide