unlock iewb vo vol2.v3.00.lab5.solutionsguide.0.01

8/13/2019 Unlock IEWB VO VOL2.v3.00.Lab5.Solutionsguide.0.01

1/69

CCIE Voice Lab Workbook Volume II Version 3.0 Lab 5 Solutions

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

Task 1.1

SW1:

vlan 11name VOICE!

vlan 12name DATA!interface range FastEthernet 0/3 - 5switchport mode accessswitchport voice vlan 11switchport access vlan 12

R2:

vlan databasevlan 11 name VOICEvlan 12 name DATAexit

!interface FastEthernet 0/1/0switchport mode trunkswitchport trunk allowed vlan 1,11,12,1002-1005switchport voice vlan 11switchport trunk native vlan 12!interface FastEthernet 0/1/1switchport mode trunkswitchport trunk allowed vlan 1,11,12,1002-1005switchport voice vlan 11switchport trunk native vlan 12

SW2:

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

!


2/69



Task 1.2

R1:! Ensure you exclude addresses

! before you configure an IOS DHCP pool!ip dhcp excluded-address 177.3.11.1 177.3.11.49ip dhcp excluded-address 177.3.11.61 177.3.11.254

ip dhcp pool PHONESnetwork 177.1.11.0 /24option 150 ip 177.1.10.10default-router 177.1.11.1

R2:ip dhcp excluded-address 177.3.11.1 177.3.11.49ip dhcp excluded-address 177.3.11.61 177.3.11.254!

ip dhcp pool PHONESnetwork 177.101.2.0 /24option 150 ip 177.1.10.10default-router 177.1.11.1

R3:ip dhcp excluded-address 177.3.11.1 177.3.11.49ip dhcp excluded-address 177.3.11.61 177.3.11.254!ip dhcp pool PHONESnetwork 177.3.11.0 /24option 150 ip 177.3.11.1option 66 ascii cucm7-pub

default-router 177.3.11.1

Task 1.3

Step 1:

R1:

ntp master 2ntp source Loopback0clock timezone PST -8

R2:

ntp source Loopback0clock timezone CST -6

R3:ntp source Loopback0clock timezone GMT 0


3/69



Step 2:

On CUCM: Navigate to System > Phone NTP Reference. Click Add New, enter the IP ofR1's Loopback:

Step 3:Navigate to System > Date/Time Group. Click CMLocal, and modify the settings for theHQ Site. Ensuring you add the NTP reference:

Add two new Date/Time groups for sites BR1 and BR2.


4/69


5/69



Step 2:

Login to the CCMAdminutility and navigate to the System > Server section of the menu.Click the Findbutton to list all available servers. If the hostnames are used, replace themwith the IP addresses 177.1.10.10 and 177.1.10.20 for the Publisher and Subscriberrespectively.


6/69


7/69



Step 5:Navigate to Call Routing > Class of Control > Partitionsthen Calling Search Spacesand click the Add a New Partition link. Add the following Partitions and Calling SearchSpaces, ensuring the CSS contains the corresponding Partition. CSS_GLOBAL shouldcontain PT_USA and PT_INTL


8/69



Step 6:Navigate to System > Device Pooland click the Findbutton to list the available devicepools. Rename the Default device pool to DP_HQ and set the Date/Time Group fieldto CMLocal in the device pool settings. Set the Calling Search Space for Auto-Registration to CSS_HQ_Device:

Copy the DP_HQ device pool and name the copy DP_BR1. Set the Date/Time Goupfor this device pool to TZ_BR1, repeat this for the Br2 site, with the proper Date/Time.

Step 7:Navigate to the System > Enterprise Parameters section of the menu. Replace theCallManager domain name in the Phone URL Parameters with the IP address of thePublisher CallManager (177.1.10.10)

Step 8:

Login to the CCMAdminutility and proceed to theSystem > Cisco Unified CM section ofthe menu. Configure the CCM-PUB server to enable Auto-Registration using theextension range 1001-1003", and enable Auto-Registration.


9/69



Create users in the CallManager corporate directory:

Step 1:Navigate to User > Add a New User. Enter hquser1 as the value for First Name,LastName and User ID fields. Set the User Password to cisco and PIN value to 12345.

Check the Enable CTI Application Use checkbox on the bottom of the page and then clickthe Insert button:

Step 2:Click the Device Associationlink on the User page and use the description HQ IP Ph1to locate the phone. Check the respective device and click the Update button when you'redone toassociate the device with the user.

Step 3:Repeat Step 1and Step 2with the usernames hquser2", and hquser3" corresponding to

HQ IP Phones 2 and 3. Check the CTI Application Use field for both users.Mark primary extensions for hquser3 as ICD extension (this will be needed by CUCCX).Finally create a new user cuccxadmin password cisco which will be used for CRS.


10/69


11/69



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 portsPort adapter is analyzed

Port adapter insertion time 6d13h agoOnboard VPN : v2.3.3EEPROM contents at hardware discovery:

WIC Slot 0:T1 (2 port) Multi-Flex Trunk WAN daughter card

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/0framing esflinecode b8zs

pri-group timeslots 1-3 service mgcp!

!! !

Jun 21 14:34:26.812: %CONTROLLER-5-UPDOWN: Controller T1 0/0, changed state toup


12/69



VORack01R1(config-controller)#Jun 21 14:34:28.812: %LINK-3-UPDOWN: Interface Serial0/0:23, changed state to up

!! Bind the Layer 3 packets to the CUCM system

!

interface serial 0/0/0:23isdn 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.20mgcp bind control source loopback 0mgcp 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 Newbutton,and follow through the steps to configure the gateway:

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


13/69



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 determinedearlier (0/0/0):

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


14/69



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

Configure the applicable settings for the gateway. The End-Point name and description areautomatically configured, and will be used later for configuration of the channel status. Allsettings requiredmust be configuredas shown below:


15/69



Continue with further configuration of the gateway. The PRI Protocol Type is automaticallyset, however you must change the Channel Selection Order. Next, uncheckthe Inhibitrestarts at PRI initialization, and checkthe Enable status polloption boxes.

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


16/69



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

Step 5:

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

Once the page has loaded, click the Advancedbutton, which will display all of theadvanced parameters:


17/69



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

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

Task 3.2

Perform the following steps to configure R2 as H.323 gateway and register it with theCallManager cluster:

Step 1:

R2:

!

! Configure the switchtype and clocking!isdn switchtype primary-ni

network-clock-participate wic 0

!controller t1 0/0/0

framing esflinecode b8zspri-group timeslots 1-3

!interface serial 0/0/0:23

isdn outgoing display-ie!! Configure the h323 gateway, binding to the loopback interface

!

interface loopback 0h323-gateway voip interface

h323-gateway voip bind scradr 177.1.254.2!

! Create the incoming dial-peers!

dial-peer voice 1 potsincoming called-number .direct-inward-dial

!


18/69



! Configure two dial-peers. One to the SUB and one to the PUB!

dial-peer voice 3120 voipdestination-pattern 312301....$session target ipv4:177.1.10.20

voice-class h323 1

!dial-peer voice 3121 voip

destination-pattern 312301....$session target ipv4:177.1.10.10

voice-class h323 1!! Configure the outgoing dial-peers

!dial-peer voice 911 potsdescription == 911 ==

destination-pattern 911port 0/0/0:23forward-digits 3

!

dial-peer voice 9911 potsdescription == 9911 ==

destination-pattern 9911port 0/0/0:23

forward-digits 3

!

dial-peer voice 900 pots

description == Local Calls ==destination-pattern 9[2-9]......$port 0/0/0:23

!dial-peer voice 901 potsdescription == Long Distance ==

destination-pattern 91[2-9]..[2-9]......$

port 0/0/0:23prefix 1!dial-peer voice 902 pots

description == International ==destination-pattern 9011Tport 0/0/0:23

prefix 011!voice service voip

h323call start slow

!


19/69



Step 2:


Enter the configuration settings for the gateway:Use the Loopback IP from R2 as the Device Name. Also define the Device Pool.

Set the significant digits to 4, and the Calling Search Space to CSS_BR1. Check theRedirecting Number IE Delivery Inbound box.


20/69



Finally, check the Display IE Delivery and Redirecting Number IE Delivery Outboundcheckboxes. Then slick save.


21/69



Task 3.3

Perform the following configuration steps on R3 to configure it as H.323 gateway:

Step 1:Configure the ISDN PRI settings and VoIP interface:

R3:

!! ISDN PRI configuration!isdn switch-type primary-net5!controller E1 1/0/0linecode hdb3framing crc4pri-group timeslots 1-3!interface Serial 1/0/0:15isdn outgoing display-ie!gateway!interface Loopback0h323-gateway voip interfaceh323-gateway voip bind srcaddr 177.1.254.3

Step 2:Configure the dial-peers to handle incoming PSTN calls

R3:!! Incoming Calls!dial-peer voice 999 potsincoming called-number .direct-inward-dial!!!

dial-peer voice 21310 voipdestination-pattern 21313...$codec g729r8no vaddtmf-relay h245-alphasession target ipv4:177.1.10.20


22/69



!! QoS marking!ip qos dscp cs3 signaling

!dial-peer voice 21311 voipdestination-pattern 21313...$codec g729r8no vaddtmf-relay h245-alphasession target ipv4:177.1.10.10preference 2!! QoS marking!ip qos dscp cs3 signaling

Step 3:Configure dial-peers to handle outgoing PSTN calls

R3:dial-peer voice 999 potsdesc == Emergencyport 1/0:15destination-pattern 999forward-digits 3!dial-peer voice 900 potsdescription == Local numbers 8 digitsdestination-pattern 9[2-8].......$port 1/0/0:15!dial-peer voice 901 potsdescription == LD 10 digitsdestination-pattern 90[2-8].........$port 1/0/0:15prefix 0!dial-peer voice 902 pots

description == Internationaldestination-pattern 900Tport 1/0/0:15prefix 00


23/69



Perform the following configuration steps on the Publisher CallManager

Step 1:


Enter the configuration settings for the gateway:Use the Loopback IP from R3 as the Device Name. Also define the Device Pool.


24/69



Set the significant digits to 4, and the Calling Search Space to CSS_BR1. Check theRedirecting Number IE Delivery Inbound box.

Finally, check the Display IE Delivery and Redirecting Number IE Delivery Outboundcheckboxes. Then slick save.


25/69



Tasks 4.2-4.4

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

Step 2:Navigate to Call Routing > Route/Hunt > Route Groupand click the Add a New RouteGrouplink. Create the following route groups: RG_HQ, RG_BR1 and RG_BR2 Step 3:Navigate to Call Routing > Route/Hunt > Route List. Click the add new button, andcreate a new Route List named RL_LOCAL:

Click save, then click the Add Route Groupbutton. Select the Standard Local RouteGroup:


26/69



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

Task 4.3-4.6

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


27/69



Step 2:

Navigate to Call Routing > Translation Pattern. Click Add New, and create the followingTranslation 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 Predot911 PT_USA / CSS_GLOBAL (Urgent)

Number Type: Subscriber / Plan: ISDNPrefix + (Called)Strip Predot

999 PT_INTL / CSS_GLOBAL (Urgent)Number Type: Subscriber / Plan : ISDNPrefix + (Called)

9[1-8]XXXXXXXX PT_INTL / CSS_GLOBAL (Not Urgent)Number Type: Subscriber / Plan: ISDNPrefix + (Called)

90[1-8]XXXXXXXXX PT_INTL / CSS_GLOBAL (Not Urgent)Number Type: National / Plan: ISDNPrefix + (Called)

900! PT_INTL / CSS_GLOBAL (Not Urgent)Number Type: International / Plan: ISDNPrefix + (Called)

*.1&*.2

PT_INTL / CSS_GLOBAL (Urgent)Number Type: International / Plan: ISDNPrefix +90017752011001 or 1002 (Called)Strip Predot

9001900XXXXXXX PT_INTL / CSS_GLOBAL (Not Urgent)

Block This Pattern (Call Rejected)Number Type: International / Plan: ISDNPrefix + (Called)


28/69



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

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

Repeat this step on the H.323 gateway, and the SIP Trunk.


29/69



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 5.1

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


30/69



Step 2:Navigate to System > Region then click the Findbutton to list available regions.Renamethe 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 MOH

HQ G.711 G.711 G.729 G.711BR1 G.711 G.729 G.711

BR2 G.711 G.711

MOH G.711

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

Step 3:Navigate to System > Device Pooland click the Findbutton to list all device pools in thesystem. For each of the device pools DP_HQ, DP_BR1 and DP_BR2 set the Regionand Location to their respective settings:


31/69



Step 4:Navigate to Device > Gatewayand click the Findbutton to list all gateways. For each ofthe devices (HQ, BR1 and BR2 gateway) depending on their site, set the Location field toLOC_HQ, LOC_BR1 or LOC_BR2 respectively.

Tasks 6.1-6.3

To configure the Music on Hold servers, perform the following steps:

Step 1:Add a new device pool named DP_MOH: copy it from DP_HQ. Ensure the Region fieldis set to REG_MOH for this device pool.

Step 2:Navigate to Media Resource > Music on Hold Server and then click theFind button. Foreach of the MoH Servers listed, set the Device Pool to DP_MOH and Location toHUB_NONE. 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 IncrementMulticast on IP Address, and then click the Updatebutton:

Repeat the same operations for the Subscriber MOH server, changing the IP to 239.1.1.2.


32/69



Step 3:In the upper right hand navigation section of the configuration page, click the "Configure

Audio Sources" link.

Next, click MOH Audio Source 1. Check the Allow Multicasting field, and then click theSave button:

Next, click the Related Link for the Music On Hold Server Configuration. Set the MaximumHops to 1 so that the MOH multicast stream will not reach the WAN, as the Br1 router willbe streaming the MOH.

Step 4:Enable multicast MOH delivery from Br1:R2:!

call-manager-fallbackmoh music-on-hold.aumulticast moh 239.1.1.1 port 16384 route 177.3.11.1 177.1.254.2

!


33/69


34/69



Step 2:

Navigate to Media Resource > Conference Bridge, then clickAdd a New ConferenceBridge link. Set the Conference Bridge Type field value to Cisco IOS EnhancedConference Bridge, Name to R1_CONF, Device Pool field valueto DP_HQ, theLocation field value to HUB_NONE, and Security Mode to Non Secure:

Register R2s dsp-farm with the CallManager cluster as transcoders per the followinginstructions:

Step 1:R2:

voice-card 0no dspfarmdsp service dspfarm!sccp local Vlan 11sccp ccm 177.1.10.10 identifier 1 version 7sccp ccm 177.1.10.20 identifier 2 version 7

sccp ip precedence 3sccp!sccp ccm group 1associate ccm 1 priority 2associate ccm 2 priority 1associate profile 1 register R2_XCODER!


35/69



dspfarm profile 1 transcodecodec g711ulawcodec g711alawcodec g729r8codec g729ar8!

! The number of xcoding sessions!maximum sessions 3associate application SCCPno shut

Step 2:

Navigate to Media Resource > Transcoder. Clickthe Add a New Transcoder link. Setthe Transcoder Type to Cisco IOS Enhanced Media Termination Point, set the DeviceName to R2_XCODER and the Device Pool field to DP_BR1


36/69



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

Step 1:Navigate to Media Resource > Media Resource Groupand create two MRGs each

containing either the Publisher or Subscriber MoH servers. Check the Use Multicast forMOH Audio box for each of the groups, and name the groups asMRG_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.


37/69



Step 2:Create three MRGLs. One for each site: MRGL_HQ, MRGL_BR1 and MRGL_BR2 perthe 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 Listto accomplish this task:


38/69



Step 3:

Navigate to System > Device Pooland change the Media Resource Group List for eachdevice pool, assigning the MRGLs to the appropriate devices pools for each site.

Task 7.1

Task 7.1

Step 1:Call Routing > Class of Control > Partitionthen click the Add a New Partition link.Name the new partition as PT_MANAGER and click the Insert button.

Step 2:

Navigate toRoute Plan > Class of Control > Calling Search Spaceand click the Add aNew Calling Search Space link. Fill in the Calling Search Space as CSS_MGR andmove the PT_MANAGER partition from Available Partition to Selected Partitions thenclick the Insert button.

Step 3:Navigate to Device > CTI Route Pointand click the Add a new CTI Route Point link.Enter RP_IPMA for the Device Name, DP_HQ for the Device Pool, set the CallingSearch Space field to CSS_MGR, set the Location field to HUB_NONE and then clickthe Save button.

Step 4:Set the Directory Number to 1XXX, Partition to PT_INTERNAL and click the Addbutton.


39/69



Step 5:

Find the URL value for IPMA Proxy mode service under the Cisco IP Manager Assistantwith Proxy Line support DocCD section. Navigate to Device > Device Settings > PhoneServicesand then click the Add New link. Enter the Service URL as:

http://177.1.10.10/ma/servlet/MAService?cmd=doPhoneService&Name=#DEVICENAME#

Set the Service Description field value to IPMA and click the Insert button:

Step 6:Navigate to System > Service Parameters. Choose the server corresponding to thePublisher CallManager and select IP Manager Assistant application. Set the field valuesper the following table. Ensure you edit the same settings on the Sub server as well.

Field Value

CTI Manager (Primary) IP Address 177.1.10.10

Route Point Device Name for ProxyMode

RP_IPMA

Cisco IPMA Server (Primary) IPAddress

177.1.10.10

Once completed click theSave button.


40/69



Perform the following steps on the Publisher CallManager to configure the manager and

assistant IP Phones:

Step 1:Navigate to Call Routing > Intercom > Intercom Route Partition. Add a new partitionnamed PT_INTERCOM. Click Save.Step 2:Navigate to Device > Device Settings > Phone Button Template. Select the templatecorresponding to the phone model such as 7960, 61, 62, 65, etc... Click the Copy button.Name the new template "IMPA Template 3+3". Set the second button to Intercom and thethird button to be a line appearance, instead of a Speed Dial:

Step 3:Navigate to Device > Phonesection and locate HQ IP Phone 1 using the Findfunction.Change the Softkey Template field to Standard Manager, and the "Button Template" toIMPA Template 3+3:


41/69



Step 4:Choose Line 1of the phone and change the Partition field to PT_MANAGER then clickthe Save button. Next, Choose Line 2and set the Intercom DN number to *1001, choosethe partition created for the Intercom line, as well as the CSS. Finally, set the speed dial to

*1002 which will point to the assistants phone:

Step 5:

Under HQ IP Phone 1 device settings click the Subscribe/Unsubscribe Services link inthe related links navigation menu. Under Select a Service menu choose IPMA, click theContinuebutton then click the Subscribe button, then click Save.

Step 6:Navigate to Device > Phoneand locate HQ IP Phone 2 using the Findbutton. Under thedevice settings ensure the Phone Button Templateis set to "IMPA Template 3+3.


42/69



Change the Softkey Template to Standard IPMA Assistant.

Step 7:Choose Line 2and set the Intercom DN number to *1002, choose the partition created forthe Intercom line, as well as the CSS. Finally, set the speed dial to *1001 which will point to

the managers phone. On the phone settings page, choose the Line 2 Add a DN link, setthe Directory Number to 1011, and the Calling Search Space to CSS_MGR. ChangeDisplay (Internal Called ID) field to IPMA Proxy Line then click the Add button.

Perform the following steps on the Publisher CallManager to create new users:

Step 1:Navigate to User Management > End User. Click Add New, and set up the following user:hqmanager as the First Name,Last Name and User ID. Set the User Password to

cisco and PIN to 12345. Check the Allow Control Of Device From CTI checkbox thenclick the Save button.

Step 2:Click the Device Associationlink on the User page. Locate HQ IP Phone 1, check thedevice on the page and click the Save button to associate the device with the user.

Step 3:Create a new user for the assistant phone. Use hqast as the First Name, Last Nameand User ID. Set the User Password to cisco and the PIN field to 12345.Check the Allow Control Of Device From CTI checkbox then click the Save button.

Step 4:Click the Device Associationlink on the User page. Locate HQ IP Phone 2, check thedevice on the page and click the Save button to associate device with the user.

Perform the following steps to configure the IPMA application user settings:

Step 1:Locate the hqmanager user. Under the Related Links menu select Manager Confguration.Uncheck the Automatic Configuration box. Set Intercom Line value to *1001 and move

line 1001 from Available Lines to Selected Lines. Set the Assistant, and click save:


43/69



Step 2:Click on the hqast user on the hqmgr page and click View Details. Uncheck the

Automatic Configuration box, and configure the assistant user with the relevant linesettings configured earlier:

Step 3:

To install the IPMA applicaton, navigate to Application > Plugins.Click the download iconnext to the Cisco Unified CallManager Assistant Console.Once the application hasdownloaded, complete the installation process.

After the application has installed, configure it for the IPMA server IP address(177.1.10.10), and hqast username. Authenticate using the password value youconfigured previously. Once the application has launched and autheticated, you can test


44/69



the IPMA configuration, by placing a call from another phone to 1001, HQ Ph2 should ring.

Task 8.1Perform 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:


45/69



Step 3:R2:ccm-manager fallback-mgcp

!applicationglobal

service alternate default!telephony-servicesrst mode auto-provision all

max-ephone 2max-dn 10ip source 177.1.254.2

dialplan-pattern 1 3123012... extension-length 4

voicemail 917752011500call-forward noan 917752011500 timeout 5call-forward busy 917752011500secondary-dialtone 9

!voice translation-rule 1rule 1 /.*/ /\0/ type any subscriber plan any isdn

!voice translation-profile subscribertranslate called 1

!voice translation-rule 2rule 1 /.*/ /\0/ type any national plan any isdn

!voice translation-profile national

translate called 2!voice translation-rule 3

rule 1 /.*/ /\0/ type any international plan any isdn!voice translation-profile intl

translate called 3!voice translation-rule 4

rule 1 /.*$....$/ /\1/!voice translation-profile vmail

translate calling 4!

dial-peer voice 1 potsincoming called-number .direct-inward-dial

!


46/69



!dial-peer voice 900 pots

destination-pattern 9[2-9]......$port 0/0/0:23translation-profile out subscriber

!

dial-peer voice 901 potsdestination-pattern 91[2-9]..[2-9]......$

prefix 1port 0/0/0:23

translation-profile out national!dial-peer voice 902 pots

destination-pattern 9011Tprefix 011port 0/0/0:23

translation-profile out intl!dial-peer voice 911 pots

destination-pattern 911

forward 3port 0/0/0:23

translation-profile out subscriber!

dial-peer voice 912 potsdestination-pattern 9911forward 3

port 0/0/0:23translation-profile out subscriber!

dial-peer voice 150 potsdestination-pattern 917752011500forward-digits 11

translation-profile outgoing vmail

port 0/0/0:23!

dial-peer voice 300 potsdestination-pattern 3...

prefix 9011442321313port 0/0/0:23!


47/69


48/69



Task 10.1

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 configurationsteps as shown below. Use the Navigation buttons at the bottom of the page to movebetween the configuration steps:

Set the number of ports to 2:

Use HQ related parameters for the Unity Call Routing configurations:


49/69



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


50/69



Use the default Line Group name:

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


51/69



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 thepreviously created Line Group, and click Save:


52/69



Step 3:Navigate to Voice Mail > Voice Mail Port Wizard. Click the link for the Hunt Pilot, andclick 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 thesettings for the Pilot: (# 1500, CSS_HQ, Check the Default Box)


53/69



Step 5:Navigate to Voice Mail > Message Waiting. Click the Add New button, and configure thetwo 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 DefaultProfile. Add the Pilot, and Mask to the configuration:


54/69



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

Step 8:Open the Cisco Unity Connection Administration subsytem, and navigate to TelephonyIntegrations > 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 theCUCM cluster for the Device Name Prefix:CiscoUM1-VI

**Do not include the 1 or 2 after the prefixname from the port numbers, this will notwork properly, and the Unity server willnever register with the CUCM

Set the IP Address to the Publishers IP


55/69



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

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


56/69



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

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


57/69



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". Uncheckthe Set for Self-enrollment at Next Login" field then click Save:


58/69



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

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


59/69



Step 5:Navigate toTools > Import Users. For the "Find Unified Communications Manager End

Users In Set the option to PhoneSystem. Click Find, and select the appropriate users.

Next, click Import. All user data will be imported, then each account will be automaticallycreated on the Unity system using the template and authentication rules created in theprevious steps.

Step 6:On the CUCM Server, Navigate toDevice > Phone. Click the DN configuration link, and

set the Forward to Voice Mail for the Busy and No Answer check boxes:


60/69



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

Task 11.1

Step 1:

On the CUCM Publisher, navigate to Device > Trunk. Create a new SIP Trunk:

Configure the trunk as shown below, using the Device Pool and Location for HQ:


61/69



Set the Destination IP to the Presence Server IP address (177.1.10.50):


62/69



Step 2:

Navigate to User Management > End User. Click add new, and create a user for the HQPhone: hquser1, Password:cisco, Pin: 12345. Click Save:

Click the Device Associationlink on the User configuration page. Locate and select HQPhone 1, then click Save Selected Changes.

Navigate back to the user page, and Set the primary extension to 1001:

Click the Add to User Grouplink near the bottom of the page. Select the Standard CTI

Enabled Group, then click Add Selected.

Finally, click Save on the user page.


63/69



Step 3:

Navigate to User Management > Application User. Click add new, and create a user forthe Presence CTI Control:CtiGw, Password:cisco, click Save. Next, click the Add to UserGrouplink near the bottom of the page. Select the Standard CTI Allow Control of AllDevices then click Add Selected:

Step 4:

Navigate to Device > Phone. Select HQ Phone 1, and set the Owner User ID to the userpreviously created, then click Save:

Step 5:

Navigate to System > Service Parameters. Select the Publisher as the server, and CallManager as the service. Locate the CUP Publish Trunk Field, and set the trunk toPRESENCE_TRUNK created above, then Click Save:

Step 6:

Navigate to System > Licensing > Capabilities Assignment. Locate and Select hquser1.Enable CUP and CUPC for the user. Click Save:


64/69



Step 7:

Navigate to System > Application Server. Click Add New, and set the type to CiscoUnified Presence Server, then click Next:

Set the Name to the Presence Hostname (CUPS7) then set the IPs, click Save:

Open the Presence Administration homepage: (177.1.10.50). Click the PresenceAdministraion Link. Complete the integration steps, as shown below:

Enter the CUCM hostname, and IP:


65/69



CUCM admin user and password cciecisco:

Security Password: cciecisco

Check the listed information, and click Confirm:


66/69



Click the Home Link to reach the Adminsitration Page. Navigate to Serviceability and underService Activation, activate all services.

Step 8:Navigate to System > Security > Incoming ACL. Click Add new, enter ALL for both fields:

Repeat this step to create an Outgoing ACL, also entering ALL.

Step 9:Navigate to System > Service Parameters. Select CUPS7, then Cisco UP SIP Proxy asthe service. Set the Proxy Domain name to cisco.com:


67/69



Step 10:Navigate to Presence > Gateways. Add a new gateway type CUCM with the Publisherinformation:

Step 10:

Navigate to Presence > Routing > Settings. Set the Listener to Default TCP:

Step 10:Navigate to Application > Cisco Unified Personal Communicator > Settings. Enter thePublisher IP for the TFTP server:


68/69



Step 10:Navigate to Application > Cisco Unified Personal Communicator > User Settings.Locate and Select hquser1 and assign the CTI profile:

Step 11:Navigate to Application > Deskphone Control > Settings. Set the Status to On, enter thepassword of the CtiGw user created in CUCM (cisco), and enter the Subscriber, thenPublisher IP Addressess:


69/69


Step 12:Ensure you have Cisco Unified Personal Communicator installed on your computer. Youcan download this application from http://www.cisco.comLaunch the application, and enter user credentials created for hquser1:

Click Log In, ensure Desk Phone mode starts, and place a call using the Dial Pad, ensuringthat HQ Phone 1 is placing the call:

unlock iewb vo vol2.v3.00.lab5.solutionsguide.0.01

Documents