Unlock IEWB VO VOL2.v3.00.Lab2.Solutionsguide.0.02

8/13/2019 Unlock IEWB VO VOL2.v3.00.Lab2.Solutionsguide.0.02

1/88

CCIE Voice Lab Workbook Volume II Version 3.0 Lab 2 Solutions

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

Task 1.1

SW1:

vlan 11

name RACK1_VOICE!vlan 12name RACK1_DATA!interface range FastEthernet 0/2 - 5switchport mode accessswitchport access vlan 12switchport voice vlan 11spanning-tree portfastcdp enable!

R2:exitvlan databasevlan 11 name RACK1_VOICEvlan 12 name RACK1_DATAexit

conf t!! IP Phone!interface range FastEthernet 0/1/0 - 1switchport mode trunk

switchport trunk allowed vlan 1,11,12,1002-1005switchport voice vlan 11switchport trunk native vlan 12cdp enable

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


2/88



Task 1.2

R1:ip dhcp pool PHONES

network 177.1.11.0 /24option 150 ip 177.1.10.10default-router 177.1.11.1

R2:ip dhcp pool PHONESnetwork 177.2.11.0 /24option 150 ip 177.1.10.10default-router 177.2.11.1

R3:ip dhcp pool PHONESnetwork 177.3.11.0 /24option 150 ip 177.3.11.1default-router 177.3.11.1


3/88



Task 2.1

Perform the following configuration steps on the Publisher CallManager:

Step 1:Use the CUCM ServiceabilitySubsystem. Navigate to Tools > Service Activation.Choose the server corresponding to the CUCM Publisher first. Activate all the servicesexcept for the following: Cisco Messaging Interface,Security Services,Cisco Certificate

Authority Proxy Function and Cisco WebDialer. Activate the same set of services, withthe exception of Cisco TFTP Server, in the Subscriber CallManager.


4/88



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.


5/88



Step 3:Navigate to System> CiscoCallManager. Name the two Servers CM_177.1.10.10, andCM_177.1.10.20 corresponding to the Publisher and Subscriber:

Step 4:

Navigate to System > Cisco CallManager Groupand click the Findbutton to list allavailable groups. Rename the Default group to CUCM_GROUP and select, then add

the Subscriber server to the group. Make sure the Publisher is placed before the subscriberin the list and the group is set for Auto-Registration by default. **Note: Once the autoregistration process is complete, the Subscriber server should be placed first in the order.This is the recommended design, for the Subscriber to perform Call Processing:


6/88



Step 5:

Navigate to Call Routing > Class of Control > Partitionsand click the Add a NewPartition link. Add a new partition named PT_INTERNAL.

Step 6:

Navigate to Call Routing > Class of Control > Calling Search Spaceand click the AddNew Calling Search Space link. Add a new CSS called CSS_HQ_DEFAULT and assignthe partition PT_INTERNAL to this CSS. Copy the new CSS and rename it toCSS_BR1_DEFAULT.


7/88



Step 7:Navigate to System > Device Pooland click the Findbutton to list the available devicepools. Rename the Default device pool to DP_HQ. Set the Calling Search Space for

Auto-Registration to CSS_HQ_DEFAULT:

Copy the DP_HQ device pool and name the copy DP_BR1

Step 8: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)


8/88



Step 9:Login to the CCMAdminutility and proceed tothe System > Cisco CallManager sectionof the menu. Configure the CUCM-PUB server to enable Auto-Registration

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.


9/88



Step 3:Repeat Step 1and Step 2with the usernames hquser2", and hquser3" corresponding toHQ 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.

Perform the IP Phone registration & configuration following the steps below:

Step 1:If you are using soft-phones, configure them to register with the CallManager server. Next,login to CCMAdminutility, navigate to Device > Phoneand click the Findbutton to list allregistered 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 Phone

numbers. Use the show cdp neighbor command on the switches to accomplish this.Using the MAC address table created, configure the respective IP Phones:

Step 2:Select the phone you want to configure and set the proper Device Pool (DP_HQ orDP_BR1), Description (e.g. HQ IP Ph1), Calling Search Space(CSS_HQ_DEFAULT for HQ Phones, CSS_BR1_DEFAULT for BR1 Phones

Step 3:Once you have finished with the device settings, click on the primary DN (Line 1). Changethe Directory Number to match the one assigned to the phone. Ensure the Partition is

set to PT_INTERNAL and change Display (Internal Called ID) to a value that matchesthe phone, e.g. HQ IP Ph1. Ensure the External Phone Number Mask matches the sitethe phone belongs to (775201XXXX , 312301XXXX')


10/88



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


11/88



Task 2.2

R3:!! NTP master is needed to keep the local clock in sync!ntp master

telephony-servicemax-ephones 2max-dn 16ip source-address 177.3.11.1 port 2000!! The no-reg option on the end of the dialplan-pattern command prevents the! gateway from registering the number pattern with the gatekeeper!dialplan-pattern 1 21313... extension 4 no-regcreate cnf-files

secondary-dialtone 9system message CallManager Express at BR2transfer-system full-consulttransfer-pattern ....call-forward pattern ....

ephone-dn 1 dual-linenumber 3001name BR2 IP Ph1

ephone-dn 1 dual-linenumber 3002name BR2 IP Ph2

!! Assign mac-addresses of your IP Phones!ephone 1mac-address 0006.D7E5.C8E1button 1:1restart

ephone 2mac-address 000C.F12F.C447button 1:2restart


12/88



Task 3.1

Step 1:

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

VORack01R1#show diagSlot 0:

C2811 Motherboard with 2FE and integrated VPN Port adapter, 2 portsPort adapter is analyzedPort 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 b8zspri-group timeslots 1-3 service mgcp!! 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

!


13/88



!mgcpmgcp 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.10ccm-manager mgcpccm-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)


14/88



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:


15/88



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 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, uncheckthe Inhibitrestarts at PRI initialization, and checkthe Enable status polloption boxes.


16/88




17/88



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


18/88



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:


19/88



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-ninetwork-clock-participate wic 0!controller t1 0/0/0framing esflinecode b8zspri-group timeslots 1-3!

interface serial 0/0/0:23isdn outgoing display-ie!! Configure the h323 gateway, binding to the loopback interface

!

interface loopback 0h323-gateway voip interfaceh323-gateway voip bind scradr 177.1.254.2!


20/88



! Create the incoming dial-peers!dial-peer voice 1 potsincoming called-number .direct-inward-dial

!! 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.20voice-class h323 1!dial-peer voice 3121 voipdestination-pattern 312301....$session target ipv4:177.1.10.10voice-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:23forward-digits 3

!

dial-peer voice 900 potsdescription == 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 potsdescription == International ==destination-pattern 9011Tport 0/0/0:23prefix 011!voice service voiph323call start slow

!


21/88



Step 2:

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

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.


22/88



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


23/88



Task 3.3

Perform the following steps to configure a gatekeeper and register the CallManager and R3with it:

Step 1:Configure R1 as a gatekeeper

R1:gatekeeperzone local ZONE_01 cisco.com 177.1.254.1no shutdown

Step 2:Configure ISDN settings for R3, set it up as a H.323 gateway and register it with the

gatekeeper:

R3:!! ISDN PRI configuration!isdn switch-type primary-net5!controller E1 1/0linecode hdb3framing crc4

pri-group timeslots 1-3!interface Serial 1/0:15isdn outgoing display-ie!gateway!interface Loopback0h323-gateway voip interfaceh323-gateway voip bind srcaddr 177.1.254.3h323-gateway voip h323-id BR2_GWh323-gateway voip id ZONE_01 ipaddr 177.1.254.1h323-gateway voip tech-prefix 1#

!! No reg is required so that R3 does not register endpoints!

ephone-dn 1 dual-linenumber 3001 no-reg

ephone-dn 1 dual-linenumber 3002 no-reg


24/88



Perform the following configuration steps on the CallManager Publisher to add a newgatekeeper-controlled trunk:

Step 1:

Run CUCMAdminutility and go to Device > Gatekeeperand click Add a NewGatekeeper. Set the IP Address field to 177.1.254.1 and the Description field to R1GK, click the Insertbutton then click the Save and Reset button:

Step 2:Navigate to the Device > Trunk section of the menu. Click the Add a New Trunkbuttonand select H.225 Trunk (Gatekeeper Controlled) for the Trunk Type then click the Nextbutton.

Configure the trunk settings per the following table:

Field Value

Device Name TRUNK_GK_HQ

Device Pool DP_HQ

Significant digits All

Calling Search Space CSS_HQ_DEVICERedirecting Number IE Delivery- Inbound

Check

Display IE Delivery Check

Redirecting Number IE Delivery- Outbound

Check

Gatekeeper Name 177.1.254.1

Terminal Type Gateway

Technology Prefix 1#

Zone ZONE_01

Click the Insertbutton then click the Reset Trunk button.


25/88



Task 3.4

R1:gatekeeper

zone prefix ZONE_01 44* gw-priority 0 TRUNK_GK_HQ_1zone prefix ZONE_01 44* gw-priority 0 TRUNK_GK_HQ_2zone prefix ZONE_01 1* gw-priority 10 TRUNK_GK_HQ_2zone prefix ZONE_01 1* gw-priority 9 TRUNK_GK_HQ_1zone prefix ZONE_01 1* gw-priority 0 BR2_GWarq reject-unknown-prefix


26/88



Task 4.2

Step 1:

Run the CUCMAdmin utility and navigate toSystem > Service Parameters then select

177.1.10.10 for the Serverand CiscoCallManager for the Service. Set the StopRouting on Unallocated Number Flag field to False.

Step 2:Create the following partitions: PT_HQ_PSTN_EMERGENCY for 911/9.911 patternsavailable to everyone at HQ, partition PT_HQ_PSTN_LOCAL_LD containing Local andLong distance patterns and partition PT_HQ_PSTN_INTL for international PSTNpatterns.

Next create partitions PT_BR1_PSTN_DEFAULT for the PSTN pattern available toeveryone in BR1 and PT_BR1_PSTN_INTL for international patterns.

Step 3:Create new and modify existing Calling Search Spaces per the following table:

Calling Search Space Partitions

CSS_HQ_RESTRICTED PT_INTERNALPT_HQ_PSTN_EMERGENCY

CSS_HQ_DEFAULTPT_INTERNALPT_HQ_PSTN_EMERGENCY

PT_HQ_PSTN_LOCAL_LD

CSS_HQ_PREMIUMPT_INTERNALPT_HQ_PSTN_EMERGENCYPT_HQ_PSTN_LOCAL_LDPT_HQ_PSTN_INTL

CSS_BR1_DEFAULTPT_INTERNALPT_BR1_PSTN_DEFAULT

CSS_BR1_PREMIUMPT_ INTERNALPT_BR1_PSTN_PREMIUMPT_BR1_PSTN_INTL

Step 4:Navigate to the Device > Phonesection of the menu and assign CSS_HQ_PREMIUM toHQ IP Phone 3 and CSS_HQ_RESTRICTED to HQ IP Phone 2.

Assign CSS_BR1_DEFAULT to BR1 IP Phone 1 and CSS_BR1_PREMIUM to BR1 IPPhone 2.


27/88



Step 5:Create the following three route groups under Route Plan > Route/Hunt > Route Groupsection of the menu: group RG_HQ containing GW_HQ, group RG_BR1 containingGW_BR1 and group RG_BR2 containing TRUNK_GK_HQ (Gatekeeper Trunk to

BR2).

Step 6:Create Route Lists under the Route Plan > Route/Hunt > Route Listsection of the menuaccording to the following table:

Route List Route Group Digits Manipulation

RG_HQ

Strip PreDot+Use External Phone Mask =On

RL_HQ_LOCAL_HQ_BAK_BR1

RG_BR1

Strip PreDot+Prefix Called Number: 1775+Use External Phone Mask =On

RG_HQ


RL_HQ_LD_HQ_BAK_BR1

RG_BR1

Strip PreDot

+Use External Phone Mask =On

RL_HQ RG_HQ



28/88



Step 7:Create the following route patterns under Route Plan > Route/Hunt > Route Pattern

Pattern Partition Route List

9.[2-9]XXXXXX PT_HQ_PSTN_LOCAL_LD RL_HQ_LOCAL_HQ_BAK_BR1

9.1[2-9]XX[2-9]XXXXXX PT_HQ_PSTN_LOCAL_LD RL_HQ_LD_HQ_BAK_BR1

911/9.911(Set Urgent PriorityFlag)

PT_HQ_PSTN_EMERGENCY RL_HQ

9.011!/9.011!# PT_HQ_PSTN_INTL RL_HQ

Do not forget to check the Provide Outside Dialtone field for every pattern that starts with9, including the 911 pattern.

Task 4.3

Additional Partitions and Calling Search Spaces required by this task have been alreadycreated with the Task 4.2solution.

Step 1:Create the following route lists:


RG_BR1Strip PreDot+Use External Phone Mask=On

RL_BR1_LOCAL_BR1_BAK_HQ

RG_HQ

Strip PreDot+Prefix Called: 1312

+Use External Phone Mask=On

RL_BR1 RG_BR1Strip PreDot+Use External Phone Mask=On


29/88



Step 2:Create the following route patterns:


9.[2-9]XXXXXXPT_BR1_PSTN_DEFAULT RL_BR1_LOCAL_BR1_BAK_HQ

9.1[2-9]XX[2-9]XXXXXXPT_BR1_PSTN_DEFAULT RL_BR1

911/9.911PT_BR1_PSTN_DEFAULT RL_BR1

9.011!/9.011!#

PT_BR1_PSTN_INTL RL_BR1

9.1800XXXXXXX(Check the RequireForced AuthorizationCode flag)

PT_BR1_PSTN_DEFAULT RL_BR1

For the pattern 9.1800XXXXXXX also specify the Authorization Level of 5.

Step 3:

Create a Forced Authorization Code. Navigate toCall Routing > Forced AuthorizationCode and click theAdd a New Forced Authorization Code link. Set the AuthorizationCode Name to FAC_1800, Authorization Code field value to 001 and AuthorizationLevel field value to 10. (Note: The authorization code can be set to any value equal to orhigher than the level set under the Route Pattern configuration.)


30/88



Task 4.4

Step 1:

Create the following two route lists (note the Calling Number Masks under the Route

Group digits manipulation section that are used to hide the original calling number):


RG_BR1

Strip PreDot+Use External PhoneNumber Mask=On

RL_HQ_TEHO_BR1_BAK_HQ(TEHO to BR1 area code)

RG_HQ

Strip PreDot+Prefix Called Number:1312

+Calling Number Mask:13123012000

RG_HQ

Strip PreDot+Use External PhoneNumber Mask=On

RL_BR1_TEHO_HQ_BAK_BR1(TEHO to the HQ area code)

RG_BR1

Strip PreDot+Prefix Called Number:1775

+Calling Number Mask:17752011000

RG_BR2

Strip PreDot+Use External PhoneNumber Mask=On+Prefix Called Number: 1#

RL_HQ_TEHO_BR2_BAK_HQ(TEHO to BR2 country/areacode, which is 4423)

RG_HQ

Strip PreDot+

Prefix Called Number: 011+Calling Number Mask:21313000


31/88



Note that for TEHO calls to the BR2 country + area code, we use the gatekeeper, andtherefore we need to add the tech-prefix used by the registered gateways. In our case thetech prefix is 1#, and so the number sent to the gatekeeper would look like1#4423XXXXXXXX.

Step 2:

Create the following route patterns corresponding to TEHO prefixes (note the UrgentPriority flag set for 9011.4423XXXXXXXX pattern this is necessary since the patternoverlaps with 9011!:


91312.[2-9]XXXXXXPT_HQ_PSTN_DEFAULT RL_HQ_TEHO_BR1_BAK_HQ

91775.[2-9]XXXXXX PT_HQ_PSTN_DEFAULT RL_BR1_TEHO_HQ_BAK_BR1

9011.4423XXXXXXXX(Set Urgent Priorityflag)

PT_HQ_PSTN_PREMIUM RL_HQ_TEHO_BR2_BAK_HQ

Step 3:Configure a dial-peer on the BR2 router, to handle incoming calls from the gatekeeper.

R3:!! This way we re-route a TEHO call as a local call!voice translation-rule 2Rule 10 /1#4423$........$/ /9\1/!voice translation-profile FROM_GKtranslate called 2!dial-peer voice 14423 voipincoming called-number 1#translation-profile incoming FROM_GKcodec g729r8

no vaddtmf-relay h245-alph


32/88



Task 4.5

Step 1:

Configure a PSTN dialplan for the BR2 IP Phones

R3:dial-peer voice 999 potsdesc == Emergencyincoming called-number .direct-inward-dialport 1/0:15destination-pattern 999forward-digits 3!dial-peer voice 900 potsdescription == Local numbers 8 digitsdestination-pattern 9[2-8].......$port 1/0:15!!(Remember to remove the Calling name)clid strip name!dial-peer voice 901 potsdescription == LD 10 digitsdestination-pattern 90[2-8].........$port 1/0:15prefix 0!dial-peer voice 902 potsdescription == LD 11 digitsdestination-pattern 90[2-8]..........$

port 1/0:15prefix 0!dial-peer voice 903 potsdescription == Internationaldestination-pattern 900.Tport 1/0:15prefix 00


33/88



Step 2:Hand outgoing tail-end hop-off VoIP calls to the CallManager: (across the gatekeeper)

R3:!! The following translations are needed! to strip the leading 900 from international calls! routed towards the gatekeeper!voice translation-rule 3Rule 10 /900$.*$/ /1#\1/

voice translation-profile TO_GKtranslate called 3

!! TEHO HQ!

dial-peer voice 9001775 voipdescription == TEHO HQdestination-pattern 9001775201....$!! (The session target RAS command indicates the call will be handled by a! gatekeeper, which will negotiate the RAS signaling.)!session target rascodec g729r8no vadpreference 1dtmf-relay h245-alphanumerictranslate outgoing TO_GK!! TEHO BR1!dial-peer voice 90013120 voipdescription == TEHO BR1destination-pattern 9001312301....$session target rascodec g729r8no vad!! Notice the preference command, which ensures the VOIP dial peer is used first!preference 1dtmf-relay h245-alph

translate outgoing TO_GK


34/88



Step 3:Configure PSTN backup dial-peers for TEHO calls:

R3:!! TEHO PSTN Backup!dial-peer voice 90017752 potsdescription == TEHO HQdestination-pattern 9001775201....$prefix 001775201port 1/0:15preference 2

dial-peer voice 90013122 potsdescription == TEHO HQdestination-pattern 9001312301....$

prefix 001312301port 1/0:15preference 2

Step 4:

Configure the CallManager to handle incoming TEHO calls from BR2 callers. First create anew partition name PT_GK_TRUNK. Next, create a new Calling Search Space calledCSS_GK_TRUNK and assign the new partition PT_GK_TRUNK along with thepreviously created partition PT_INTERNAL. Assign the new CSS to the gatekeeper trunkyou configured previously under the Device > Trunksection of the menu.

Step 5:Then add the following route patterns under Route Plan > Route/Hunt > Route Pattern:


1#1775.XXXXXXX PT_GK_TRUNK RL_HQ

1#1312.XXXXXXX PT_GK_TRUNK RL_BR1

We specify patterns in the format they are received from the gatekeeper - that is, with thetech-prefix in front of each number. The PreDot digit stripping instruction at the Route Listlevel automatically strips off anything that is unnecessary.


35/88



Task 4.6

Step 1:Configure R3 for abbreviated dialing. Note that each abbreviated pattern has a

corresponding PSTN backup.

R3:dial-peer voice 1000 voipdestination-pattern 1...$session target rascodec g729r8no vadpreference 1dtmf-relay h245-alphanumerictech-prefix 1#1775201!dial-peer voice 1001 pots

destination-pattern 1...$preference 2forward-digits 4prefix 001775201!dial-peer voice 2000 voipdestination-pattern 2...$session target rascodec g729r8no vadpreference 1dtmf-relay h245-alphanumerictech-prefix 1#1312301

!dial-peer voice 1001 potsdestination-pattern 2...$preference 2forward-digits 4prefix 001312301

Step 2:Add two translation patterns to the PT_GK_TRUNK partition to handle the incoming callsto abbreviated on-site numbers correctly:

Pattern Partition DDI Calling Search Space

1#1775201.1XXX PT_GK_TRUNK PreDot CSS_HQ_DEFAULT

1#1312301.2XXX PT_GK_TRUNK PreDot CSS_BR1_DEFAULT


36/88



Step 3:For abbreviated dialing from the CallManager phones to the 3XXX pattern, create threenew route-lists. The first route-list is used to call the 3XXX pattern by simply placing a callvia the gatekeeper. The next two implement a call backup option, using international dialing

via the respective on-site gateway.


RL_3XXX_GK RG_BR2 Prefix Called: 1#44232131

RG_BR2 Prefix Called: 1#44232131

RL_BR1_3XXX_GK_BAK_BR1RG_BR1

Prefix Called: 01144232131+Use External Phone Mask=On

RG_BR2 Prefix Called: 1#44232131

RL_HQ_3XXX_GK_BAK_HQ

RG_HQ

Prefix Called: 01144232131

+Use External Phone Mask=On

Step 4:Next create a new partition called PT_3XXX_SIMPLEAdd this partition to CSSesCSS_HQ_DEFAULTand CSS_BR1_DEFAULT

Next create the following route patterns:


3XXX PT_3XXX_SIMPLE RL_3XXX_GK

3XXX PT_BR1_PSTN_INTL RL_BR1_3XXX_GK_BAK_BR1

3XXX PT_HQ_PSTN_INTL RL_HQ_3XXX_GK_BAK_HQ


37/88



Step 5:Modify the translation rule on the BR2 router, to handle incoming calls representingabbreviated dialing numbers:

R3:voice translation-rule 2Rule 1 /1#44232131$....$/ /\1/

!! The above translation rule will match numbers containing the pattern! 1#44232131.... and translate them to .... (Pattern 1 \1)!

Tasks 5.1 - 5.2

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 72Kbps (3x24Kbps):

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.729 G.729 G.711BR1 G.711 G.729 G.729

BR2 G.711 G.729MOH G.711


38/88



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:

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.

Step 4:Configure the gatekeeper settings in R1 as follows:

R1:

gatekeeperbandwidth total default 48

! The bandwidth total default command specifies the default bandwidth for all! zones. The bandwidth value, in this case 48 is in Kbps.


39/88



Task 6.1 6.2

Perform the following steps to add the DSP resources from R1 as a conference bridge forthe CUCM cluster:

Step 1:

R1:

voice-card 0no dspfarmdsp service dspfarm

sccp local fa 0/0.11sccp ccm 177.1.10.20 identifier 1 version 7sccp ccm 177.1.10.10 identifier 2 version 7sccp ip precedence 3sccp

sccp ccm group 1associate ccm 1 priority 1associate ccm 2 priority 2associate profile 1 register R1_CONFassociate profile 2 register R1_XCODER

dspfarm profile 1 conferenceassociate application sccpno shut

dspfarm profile 2 xcodeassociate application sccp

maximum-sessions 1no shut

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:


40/88



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 7sccp ip precedence 3sccp!sccp ccm group 1associate ccm 1 priority 2associate ccm 2 priority 1

associate profile 1 register R2_XCODER!dspfarm profile 1 transcodecodec g711ulawcodec g711alawcodec g729r8codec g729ar8!! The number of xcoding sessions!


41/88



!maximum sessions 3associate application SCCPno shut

Step 2:

Navigate to Media Resource > Transcoder. Clickthe Add a New Transcoder link. Add anew Transcoder for R1 and R2. The example below is for R2. Set the Transcoder Type toCisco IOS Enhanced Media Termination Point, set the Device Name to R2_XCODERand the Device Pool field to DP_BR1


42/88



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 eachcontaining 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 HQ and BR1 transcoders and name the groupsMRG_XCODER_HQ and _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.


43/88



Step 2:Create two MRGLs. One for each site: MRGL_HQ, MRGL_BR1 per the following table:

MRGL Name MRG List

MRGL_HQ

MRG_XCODER_BR1MRG_CFB_HWMRG_MOH_SUB_MCASTMRG_MOH_PUB_MCAST

MRGL_BR1

MRG_XCODER_BR1MRG_CFB_HWMRG_MOH_SUB_MCASTMRG_MOH_PUB_MCAST

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

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.


44/88



Tasks 6.2 - 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_HQ for this device pool.

Step 2:Enable the use of the G.729 codec for Music on Hold. Navigate to System > ServiceParameters and select177.1.10.10 as the ServerandIP Voice Media Streaming

Application as the Service. SetSupported MoH CodecstoG711mulaw andG729AnnexA (**Note that you must use Control + Click to select both Codecs)

Step 3: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.


45/88



Step 4: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 4 so that the MOH multicast stream will reach Br1, and Br2:

Step 5:

Enable multicast routing at each site:R1:ip multicast-routing!interface FastEthernet 0/0.11ip pim dense-mode

!

interface FastEthernet 0/0.10ip pim dense-mode

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


46/88



R2:ip multicast-routing!interface Vlan 11ip pim dense-mode

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

!interface Loopback0ip pim dense-mode

Task 7.1

Use the examples for B-ACD parameters from the Cisco Documentation to build your owncustom B-ACD script. Find the following section in the Cisco Documentation: (DocCD)http://www.cisco.com/web/psa/products/index.html

Voice and Unified Communications > Call Control > Cisco Unified CommunicationsManager Express > Configuration Guides > Cisco Unified CME B-ACD and Tcl Call-Handling Applications

Step 1:Create a new hunt-pilot in R3 and list two extensions in the hunt-group. Create a dial-peer

to handle incoming calls to the pilot number:

R3:dial-peer voice 3000 potsservice acdaaport 1/0:15incoming called-number 21313000!ephone-hunt 1 sequentialpilot 3100list 3001, 3002timeout 6no-reg pilot


47/88



Step 2:Configure the B-ACD application settings:

R3:

applicationservice callq flash:app-b-acd-2.1.2.2.tclparam queue-manager-debugs 1param aa-hunt1 3100param number-of-hunt-grps 1param queue-len 10

!service acdaa flash:app-b-acd-aa-2.1.2.2.tclparamspace english location flash:paramspace english index 0paramspace english language enparam aa-pilot 21313000param number-of-hunt-grps 1param service-name callq

param handoff-string acdaaparam second-greeting-time 60param drop-through-option 1param drop-through-prompt _bacd_welcome.auparam call-retry-timer 30param max-time-call-retry 600param voice-mail *3000param max-time-vm-retry 2

Step 3:

Create a special ephone-dn to be used for voice-mail redirects:

R3:

ephone-dn 10number *3... no-regcall-forward all 3500

Task 8.1Step 1:In the Publisher CallManager navigate to the System > SRSTsection of the menu and adda new SRST reference named SRST_BR1 pointing at the IP address of R2 177.1.254.2. Assign this SRST reference to the device pool DP_BR1 under the System> Device Poolsection of the menu


48/88



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

R!! Translation-profile to trim DID numbers!voice translation-rule 1Rule 1 /312301$....$$/ /\1/!voice translation-profile DIDtranslate called 1

Step 3:!! Configure fallback from MGCP application!call application alternate defaultccm-manager fallback-mgcp!call-manager-fallbackmax-ephone 2secondary-dialtone 9max-dn 8ip source-address 177.2.11.1

system message primary SRST services at BR1call-forward pattern .Ttransfer-pattern .Ttransfer-system full-consultalias 1 2000 to 2001alias 2 2000 to 2002max-conferences 3


49/88



Task 9.1

Tasks 9.1

R1:map-class frame-relay DLCI_101frame-relay cir 512000frame-relay mincir 512000frame-relay bc 5120frame-relay be 0frame-relay fair-queue

!! We need to turn on FRF.12 in order to engage! PQ/WFQ mechanics. Since we dont want any actual! fragmentation, we set the frag size to 1500!

frame-relay fragment 1500

!! Bandwidth is allocated for 3 cRTP G.729 calls (11.6 Kbps each)!frame-relay ip rtp priority 16384 16383 36

map-class frame-relay DLCI_201frame-relay cir 384000frame-relay mincir 384000frame-relay bc 3840frame-relay be 0frame-relay fair-queueframe-relay fragment 1500frame-relay ip rtp priority 16384 16383 36!interface Serial 0/0/1:0frame-relay traffic-shaping!interface Serial 0/0/1:0.1frame-relay ip rtp header-compressionframe-relay interface-dlci 101class DLCI_101

!interface Serial 0/0/1:0.2frame-relay ip rtp header-compressionframe-relay interface-dlci 201

class DLCI_201


50/88



R2:map-class frame-relay DLCI_101frame-relay cir 512000frame-relay mincir 512000

frame-relay bc 5120frame-relay be 0frame-relay fair-queueframe-relay fragment 1500frame-relay ip rtp priority 16384 16383 30!interface Serial 0/0/1:0frame-relay traffic-shaping!interface Serial 0/0/1:0.1frame-relay ip rtp header-compressionframe-relay interface-dlci 101class DLCI_101

R3:map-class frame-relay DLCI_201frame-relay cir 384000frame-relay mincir 384000frame-relay bc 3840frame-relay be 0frame-relay fair-queueframe-relay fragment 1500frame-relay ip rtp priority 16384 16383 36!interface Serial 1/1:0frame-relay traffic-shaping!

interface Serial 1/1:0.1frame-relay ip rtp header-compressionframe-relay interface-dlci 201class DLCI_201


51/88



Tasks 10.1-10.2

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:


52/88



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

Use the default Line Group name:


53/88



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

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


54/88



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:


55/88



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)


56/88



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:


57/88



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


58/88



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:


59/88



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:


60/88



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:


61/88



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

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


62/88



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

Use the table below to enter the User Information:

**Repeat this step to configure theremaining users.

Field Value

First Name HQ

Last Name IP Ph1Display Name HQ IP Ph1

Extension 1001

Alias HQ IP Ph1


63/88


64/88



Tasks 10.3

Configure R3 for CUE integration:

Step 1:Allow VoIP calls to Cisco Unity Express, using the G.729 codec. A transcoder must beregistered with the local CME to make this possible:

R3:voice service voipallow-connection h323 to sip!voice-card 1no dspfarmdsp services dspfarm

!sccp local FastEthernet0/0.11sccpsccp ccm 177.3.11.1 priority 1sccp ip precedence 3!! Disable VAD for transcoding sessions!dspfarm transcoder maximum sessions 3dspfarm codec g729 vad disabledspfarm

!! Register DSP farm with the CME

!telephony-servicesdspfarm units 1sdspfarm transcode sessions 3

Step 2:

Configure the CallManager Express System for integration with CUE. Create a dial-peer,setup the voicemail pilot number, MWI extensions and enable the HTTP server in order forCUE to be able to interact with CME.

R3:telephony-servicevoicemail 3500web admin system name administrator password ciscodn-webedittime-webedit!ip http serverip http path flash:


65/88



!! Service-Engine configuration!interface Service-Engine 0/0ip unnumbered FastEthernet 0/0.11

service-module ip address 177.3.11.254 255.255.255.0service-module ip default-gateway 177.3.11.1no shutdown!ip route 177.3.11.254 255.255.255.255 Service-Engine 0/0

!! Translation profile to simulate Voice-Mail mask! Essentially shrink all numbers down to 4 digits!voice translation-rule 1Rule 1 /.*$....$$/ /\1/

!

voice translation-profile TO_VOICEMAILtranslate calling 1translate called 1translate redirect 1

!! Abbreviated number to access VM pilot. Notice the number expansion!num-exp 3500 21313500

!! DID number to access Voicemail!dial-peer voice 21313500 voip

destination-pattern 21313500session protocol sipv2session target ipv4:177.3.11.254dtmf-relay sip-notifycodec g711ulawmax-conn 3translation-profile outgoing TO_VOICEMAIL!!! MWI Numbers!ephone-dn 15number 3998.... no-reg

mwi on!ephone-dn 16number 3999.... no-regmwi off


66/88



Step 3:Perform the following steps in the CUE module for integration with the CME system:

Rack1R3#service-module Service-Engine 0/0 sessionTrying 177.3.11.1, 2025 ... OpenCUE>CUE> enPassword:CUE# offline!!!WARNING!!!: If you are going offline to do a backup, it is recommendedthat 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 dataon the system to be erased. This operation is not reversible.

Do you wish to continue[n]? : yRestoring the system. Please wait .....doneSystem will be restored to factory default when it reloads.

Press any key to reload:

IMPORTANT:: Welcome to Cisco Systems Service EngineIMPORTANT:: post installation configuration tool.IMPORTANT::IMPORTANT:: This is a one time process which will guideIMPORTANT:: 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 haltedIMPORTANT:: so it can be safely removed from the router.IMPORTANT::

Do you wish to start configuration now (y,n)? yAre 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, insteadIMPORTANT:: of IP addresses like 1.100.10.205 for servers used by CUE. In orderIMPORTANT:: to configure DNS you must know the IP address of at least one of yourIMPORTANT:: DNS Servers.

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

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


67/88



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 Ocean2) Americas 5) Asia 8) Europe3) Antarctica 6) Atlantic Ocean 9) Indian Ocean

#? 8

Please select a country.1) Albania 16) Greece 31) Portugal2) Andorra 17) Hungary 32) Romania

3) Austria 18) Ireland 33) Russia4) Belarus 19) Italy 34) San Marino5) Belgium 20) Latvia 35) Slovakia6) Bosnia & Herzegovina 21) Liechtenstein 36) Slovenia7) Britain (UK) 22) Lithuania 37) Spain8) Bulgaria 23) Luxembourg 38) Sweden9) Czech Republic 24) Macedonia 39) Switzerland

10) Denmark 25) Malta 40) Turkey11) Estonia 26) Moldova 41) Ukraine12) Finland 27) Monaco 42) Vatican City13) France 28) Netherlands 43) Yugoslavia14) Germany 29) Norway15) 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) Yes2) No

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

Enter administrator user ID:(user ID): administrator


68/88



Enter password for : administrator(password): cisco

Confirm password for by reentering it:(password): cisco

Step 4:Run the CUE Web-Init dialog (the CME system must be pre-configured already with theHTTP server enabled). Open the URL http://177.3.11.254/Web in your browser then loginwith the username administrator and the password cisco. Select the link RunInitialization Wizard.

Step 5:On the CallManager Express Login page, enter the hostname 177.3.YY1.1 for theCallManager IP address and the login/password you configured under telephony-service

earlier (administrator/cisco). Skip the Import CME Usersstep.

Step 6:

On the Defaults page check Blank password and Blank PIN fields. On the CallHandlingpage set Voice Mail Number to 3500, select MWI On Number as 3998.and MWI Off Number as 3999.. Finish the WebInit process.

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

CUE:conf t

!! Users!username br2user1 createusername br2user2 create!username br2user1 phonenumber 3001username br2user2 phonenumber 3002!voicemail mailbox owner "br2user1"no tutorial

end mailbox!voicemail mailbox owner "br2user2"no tutorialend


69/88



Task 10.4

Perform the following steps in the Cisco Unity Express CLI:

CUE:!! Group!groupname br2group creategroupname br2group member br2user1groupname br2group member br2user2groupname br2group phonenumber 3000!! Group Delivery Mailbox!voicemail mailbox owner "br2group"no tutorialend mailbox

!voicemail mailbox owner "br2user1"zerooutnumber 3001!voicemail mailbox owner "br2user2"zerooutnumber 3002end!username br2user1 pin 12345username br2user2 pin 12345

Task 11.1

Perform the following configuration steps to configure the JTAPI subsystem:

Step 1:Perform the following configuration steps to configure the JTAPI subsystem:

Step 1:

Login to the CUCCX machine using the following information:

Field Value

IP Address 177.1.10.40

Username (Windows) Administrator Password (Windows) cciecisco

Username (CUCCX Initilization) AdministratorPassword (CUCCX Initilization) ciscocisco

JTAPI Username/Password jtapi/cisco

RMCM Username/Password rmcm/cisco


70/88



Launch the CUCCX adminsitration using the Application Administration Internet Explorershortcut 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)


71/88



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)


72/88



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

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


73/88



Set the following System Parameters:

Choose the language:

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

The installation is now complete. Any JTAPI errors can be ignored, as they will be resolvedlater. Close the browser, then open it once again, and login with the cuccxadmin user.


74/88



Step 2:

Navigate to Subsystems > Cisco Unified CM Telephony. Click the Add a New CiscoUnified CM Telephony Call Control Group link. Fill in the fields using the table below:

Field Value

Number of CTI Ports 2

Starting Directory Numbers 1401Device Name Prefix CTI

Device Pool DP_HQ

Location LOC_HQ

AAR Group AAR_HQ

External Phone Number Mask 775201XXXXDisplay CTI Ports

Click the Addbutton.

Perform the following steps to configure the CallManager system:

Step 1:

Navigate to User > Application User. Find the user name rmcm. Select the devicecorresponding to the HQ IP Phone 3. Check the No Primary Extension and No ICDExtension fields then click the Update button. Repeat this step to associate the rmcmuser 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:


75/88



Step 3:

Navigate toDevice > Device Settings >IP Phone Servicesand click the Add a New IPPhone Servicelink

Enter the Service Name as IPPA and the Service URL as:http://177.1.10.10:6293/ipphone/jsp/sciphonexml/IPAgentInitial.jsp

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

Step 4:

Navigate to the Device > Phonesection of the menu and locate HQ IP Phone 3. On thePhone Configuration page click the Subscribe/Unsubscribe servicesRelated links, thenchoose IPPA from the drop-down list click Continueand 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 listlink and set theResource Group List Name to RG_DEFAULT then click the Addbutton:


76/88



Step 2:

Navigate to the Resourcessection and click on the hquser3. Change the ResourceGroup field to RG_DEFAULT then click the Updatebutton.

Step 3:

Click the Contact Service Queueslink then click the Add a New Contact Queuelink. Set

Contact Service Queue Name to CSQ_DEFAULT and set the Resource Pool SelectionModel to Resource Group Click the Nextbutton, then choose the Resource GroupRG_DEFAULT and click the Addbutton.

Step 4:

Navigate to Application > Application Managementthen click the Add a NewApplicationlink. Set Application Type to Cisco Script Application and click the Nextbutton.


77/88



Step 5:

Set the Name field to ICD, Maximum Number of Sessions to 2, and the Script fieldto icd.aef.Click the CSQ parameter check-box and set the parameter value toCSQ_DEFAULT and then click the Addbutton:

Step 6:

Click the Add a New Trigger link set Trigger Type to CM Telephony and set the triggerparameters according to the following table:

Field Value

Directory Number 1400

Maximum Number of Sessions DefaultCall Control Group JTAPI Group #0

Device Pool DP_HQ

Location HUB_NONEExternal Phone Number Mask 775201XXXX

Display ICD Port

Click the Addbutton.

Step 7:Navigate to System > Control Centerthen click the name corresponding to your server.Select the CUCCX Engine application and the click the Restartbutton.


78/88



Task 11.2

Step 1:Run the CRS Editorapplication, open the default script icd.aef and save it in the Default

repository under the name my_icd.aef.

Step 2:Add a new script parameter named QueueDepth of type int, set its default value to 3and check the Parameter checkbox. Add a new variable of type int to store the numberof calls queued and name it iOnQueue. Attach a label named END to the Terminatestep at the end of the script.

Step 3:Add a new step IPCC Express::Get Reporting Statistics right after the Accept step in the

beginning of the ICD script. Set Report Object to Overall IPCC Express set Field toContacts Waiting and set to save Result Statistics in iOnQueue variable.

Step 4:Add a General::If step after the Get Reporting Statistics step in the script. Compare theiOnQueue variable to the QueueDepth constant, and add a General::Goto step underthe True branch of the If step targeted at the END label.Step 5:Run CRSApplication Administration then navigate to the Applications > ApplicationManagement section of the menuand choose theICDapplication. Change the Script

field to my_icd.aef and set CSQ parameter to CSQ_DEFAULT. Ensure theQueueDepth parameter is set to 3.


79/88



Task 12.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:


80/88



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

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:


81/88



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 CTIEnabled Group, then click Add Selected.

Finally, click Save on the user page.

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:


82/88



Step 6:

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

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:


83/88



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:

CUCM admin user and password cciecisco:

Security Password: cciecisco


84/88


85/88



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:


86/88



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, then

Publisher IP Addressess:


87/88


88/88


Unlock IEWB VO VOL2.v3.00.Lab2.Solutionsguide.0.02

Documents

Transcript of Unlock IEWB VO VOL2.v3.00.Lab2.Solutionsguide.0.02