task 1 - ines3. · task 1.2 r1:! ensure you exclude addresses! before you configure an ios dhcp...

CCIE Voice Lab Workbook Volume II Version 3.0 Lab 1 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/1 - 2 switchport mode trunk switchport trunk allowed vlan 1,11,12 switchport voice vlan 11 switchport trunk native vlan 12 R2: vlan database vlan 11 name VOICE vlan 12 name DATA exit ! interface FastEthernet 0/1/0 switchport mode trunk switchport trunk allowed vlan 1,11,12,1002-1005 switchport voice vlan 11 switchport trunk native vlan 12 ! interface FastEthernet 0/1/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 FastEthernet 0/1 switchport mode trunk switchport trunk allowed vlan 1,11,12 switchport voice vlan 11 switchport trunk native vlan 12 ! interface FastEthernet 0/2 switchport mode trunk switchport trunk allowed vlan 1,11,12 switchport voice vlan 11 switchport trunk native vlan 12 !



Task 1.2 R1: ! Ensure you exclude addresses ! before you configure an IOS DHCP pool ! ip dhcp excluded-address 177.1.11.1 177.1.11.49 ip dhcp excluded-address 177.1.11.101 177.1.11.199 ip dhcp pool PHONES network 177.1.11.0 /24 option 150 ip 177.1.10.10 option 66 ip 177.1.10.10 default-router 177.1.11.1 R2: ip dhcp excluded-address 177.2.11.1 177.2.11.49 ip dhcp excluded-address 177.2.11.101 177.2.11.199 ! ip dhcp pool PHONES network 177.101.2.0 /24 option 150 ip 177.1.10.10 option 66 ip 177.1.10.10 default-router 177.1.11.1 R3: ip dhcp excluded-address 177.3.11.1 177.3.11.49 ip dhcp excluded-address 177.3.11.101 177.3.11.199 ! ip dhcp pool PHONES network 177.3.11.0 /24 option 150 ip 177.3.11.1 option 66 ip 177.1.10.10 default-router 177.3.11.1

Task 1.3 R1: ntp master 2 ntp source Loopback0 clock timezone PST -8 ntp authentication-key 1 md5 CISCO R2: ntp authenticate ntp authentication-key 1 md5 CISCO ntp trusted-key 1 ntp server 177.1.254.1 key 1 ! ntp source Loopback0 clock timezone CST -6



R3: ntp authenticate ntp authentication-key 1 md5 CISCO ntp trusted-key 1 ntp server 177.1.254.1 key 1 ! ntp source Loopback0 clock timezone GMT 0

Tasks 2.1 - 2.3 Perform the following configuration steps on the Publisher CallManager: Step 1: 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 2: Login to the CCMAdmin utility and navigate to the System > Server section of the menu. Click the Find button to list all available servers. If the hostnames are used, replace them with the IP addresses – “177.1.10.10” and “177.1.10.20” – for the Publisher and Subscriber respectively.



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

Step 4: Navigate to System > Cisco CallManager Group and click the Find button to list all available 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 subscriber in the list and the group is set for Auto-Registration by default. **Note: Once the auto registration 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:



Step 5: Navigate to System > Phone NTP Reference. Click Add New, and create references for each site, corresponding to the Loopback address of each router:

Step 6: Navigate to System > Date/Time Group and click the Find button to list all available groups. Rename the “CMLocal” group to “TZ_PST” and ensure it is set to GMT-8. Add the NTP reference created in the previous step. Click the Copy button to add a new group named “TZ_CST” with time offset of GMT-6. For this date/time group, change the format to “Y/M/D“ and 12 hour to match the provided LCD display layouts (per Task 2.3 requirements). Click Copy once again to create “TZ_GMT” with the GMT offset set to “0”.



Step 7: Navigate to Call Routing > Class of Control > Partitions and click the Add a New Partition link. Add a new partition named “PT_INTERNAL”.

Step 8: Navigate to Call Routing > Class of Control > Calling Search Space and click the Add New Calling Search Space link. Add a new CSS called “CSS_HQ_DEFAULT” and assign the partition “PT_INTERNAL” to this CSS. Copy the new CSS and rename it to “CSS_BR1_DEFAULT”. Copy the CSS once again and give the copy a name of “CSS_BR2_DEFAULT”:



Step 9: 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 “Date/Time Group” field to “TZ_PST” in the device pool settings. Set the “Calling Search Space for Auto-Registration” to “CSS_HQ_DEFAULT”:

Copy the “DP_HQ” device pool and name the copy “DP_BR1”. Set the “Date/Time Goup” for this device pool to “TZ_CST”, repeat this for the Br2 site, with the proper Date/Time. Step 10: Navigate to the System > Enterprise Parameters section of the menu. Replace the CallManager domain name in the Phone URL Parameters with the IP address of the Publisher CallManager (“177.1.10.10”)



Step 11: Login to the CCMAdmin utility and proceed to the System > Cisco CallManager section of the menu. Configure the “CCM-PUB” server to enable Auto-Registration using the extension range “1001-1010”, partition “PT_INTERNAL”:

SIP Phone Conversion:

Step 1: Create a new Phone Template: Navigate to Bulk Administration > Phones > Phone Template. Click Add New, then select 7960 as the Phone Type:



Next, select SIP as the Device Protocol:

Adjust the following parameters shown in the screenshot. Note that any highlighted area indicates a required parameter. All other fields can be left to their default settings. Once all of the fields have been set, ensure you click save:



Step 2: Navigate to Bulk Adminsitration > Phones > Migrate Phones > SCCP to SIP. From this page, you must perform a search function to limit the results to the phone you want to convert. Once you have located the phone, click next: Select the Phone Template Name, ensure the Reset Phones option is checked, and check the Run Immediately option. Then click submit:

Navigate to Device > Phone, and click find to display all phones. HQ IP Ph2 will now be displayed, however the state will show rejected.



In order to correct the issue of the phone being rejected, the auto-registration Enterprise Parameters must be modified to support SIP registration. Navigate to System > Enterprise Parameters. Change the Auto Registration Phone Protocol to SIP. Click save, then reset for the changes to take place:

Once all devices have reset, navigate back to Device > Phone. Confirm that all phones are registered, including Br1 IP Ph2 as a SIP phone:



Create users in the CallManager corporate directory: Step 1: Navigate to User > Add a New User. Enter “hquser1” as the value for “First Name”,“Last Name” 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 click the Insert button:

Step 2: Click the Device Association link on the User page and use the description “HQ IP Ph1” to locate the phone. Check the respective device and click the Update button when you're done to associate the device with the user.

Step 3: Repeat Step 1 and Step 2 with 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.



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 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 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” or “DP_BR1” or “DP_BR2” ), “Description” (e.g. “HQ IP Ph1”), “Calling Search Space” (“CSS_HQ_DEFAULT” for HQ Phones, “CSS_BR1_DEFAULT” for BR1 Phones and “CSS_BR2_DEFAULT” for BR2 Phones) Step 3: Once you have finished with the device settings, click on the primary DN (Line 1). Change the “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 matches the phone, e.g. “HQ IP Ph1”. Ensure the “External Phone Number Mask” matches the site the phone belongs to (“775201XXXX” , “312301XXXX” or “2131XXXX” respectively)



Repeat Steps 2-3 until you have all phones configured. 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 ! ! ! <Notice the console messages displayed below. The T1 controller ! Interface has come up, in addition to a new Serial interface that has ! been automatically created by the configuration (Serial 0/0/0:23)>



! Jun 21 14:34:26.812: %CONTROLLER-5-UPDOWN: Controller T1 0/0, changed state to up 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: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

Task 3.2 Perform the following configuration steps on R2: Step 1: R2: ! ! Configure the switchtype and clocking ! isdn switchtype primary-ni network-clock-participate wic 0 ! ! Configure the T1 ! controller t1 0/0/0 framing esf linecode b8zs pri-group timeslots 1-3 ! ! Enable IE delivery for the T1 ! interface serial 0/0/0:23 isdn outgoing display-ie ! ! Bind signaling and media to the most reliable interface ! voice service voip sip bind all source-interface loopback 0 ! ! Set the SIP INVITE timer to the lowest possible setting



! sip-ua timer trying 100 ! ! ! Configure the incoming dial-peer ! dial-peer voice 1 pots incoming called-number . direct-inward-dial ! ! Configure two dial-peers. One to the SUB and one to the PUB ! Add the session protocol statement ! dial-peer voice 3120 voip destination-pattern 312301....$ session target ipv4:177.1.10.20 session protocol sipv2 ! dial-peer voice 3121 voip destination-pattern 312301....$ session target ipv4:177.1.10.10 session protocol sipv2 ! ! Configure the outgoing dial-peers ! dial-peer voice 911 pots description == 911 == destination-pattern 911 port 0/0/0:23 forward-digits 3 ! dial-peer voice 9911 pots description == 9911 == destination-pattern 9911 port 0/0/0:23 forward-digits 3 ! dial-peer voice 900 pots description == Local Calls == destination-pattern [2-9]......$ port 0/0/0:23 ! dial-peer voice 901 pots description == Long Distance == destination-pattern 1[2-9]..[2-9]......$ port 0/0/0:23 prefix 1 ! dial-peer voice 902 pots description == International == destination-pattern 011T port 0/0/0:23 prefix 011



! ! Task 4.4 (hide calling number) ! clid strip ! Step 2: On the CUCM Publisher server, navigate to Device > Trunk. Click the Add New button, and follow through the steps to configure the gateway:

Set the Device Name and Device Pool, leave all other settings to their defaults.



Set the Significant Digits filed to 4. Enable Inbound/Outbound Header delivery.

Set the destination address to the loopback IP of R2. Select the following SIP settings, then click Save, and Reset.



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/0 linecode hdb3 framing crc4 pri-group timeslots 1-3 ! interface Serial 1/0/0:15 isdn outgoing display-ie ! gateway ! interface Loopback0 h323-gateway voip interface h323-gateway voip bind srcaddr 177.1.254.3



Step 2: Create a new H.323 class and set H.225 timeout values: R3: voice class h323 1 h225 timeout tcp establish 1 Step 3: Configure the dial-peers to handle incoming PSTN calls R3: ! ! Incoming Calls ! dial-peer voice 999 pots incoming called-number . direct-inward-dial ! ! ! dial-peer voice 21310 voip destination-pattern 21313...$ codec g729r8 no vad dtmf-relay h245-alpha session target ipv4:177.1.10.20 voice-class h323 1 ! ! QoS marking ! ip qos dscp cs3 signaling ! dial-peer voice 21311 voip destination-pattern 21313...$ codec g729r8 no vad dtmf-relay h245-alpha session target ipv4:177.1.10.10 preference 2 ! ! QoS marking ! ip qos dscp cs3 signaling voice-class h323 1



Step 4: Configure dial-peers to handle outgoing PSTN calls 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 [2-8].......$ port 1/0/0:15 ! dial-peer voice 901 pots description == LD 10 digits destination-pattern 0[2-8].........$ port 1/0/0:15 prefix 0 ! dial-peer voice 902 pots description == International destination-pattern 00T port 1/0/0:15 prefix 00 Perform the following configuration steps on the Publisher CallManager Step 1: On the CUCM Publisher server, navigate to Device > Gateway. Click the Add New button, and follow through the steps to configure the gateway:

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



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

Finally, check the Display IE Delivery and Redirecting Number IE Delivery – Outbound checkboxes. Then slick save.



Tasks 4.2-4.4 Step 1: Navigate to Service > 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 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 Br1 site:

Step 5: Navigate to Call Routing > Route/Hunt > Route Pattern. Create a new Route Pattern to 911. Set the partition to PT_INTERNAL. Ensure the Urgent Priority check box is marked. Set the Gateway/Route List as RL_LOCAL:



Set the Calling Party Number Type to Subscriber. Then click save:



Task 4.3-4.6 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 > Class of Control > Partition, and Calling Search Space. Create the following Partitions and CSSs:

**NOTE: All CSSs should contain only the Partitions with the same name, except for CSS_X_DEVICE which should contain the relevant country partition. (ex. CSS_HQ_DEVICE-(PT_USA), CSS_BR2_DEVICE-(PT_UK), etc…)



Step 3: 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: ISDN Prefix + (Calling & Called) Strip Predot (Discard Digits)

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

9.011! PT_USA / CSS_GLOBAL (Not Urgent) Number Type: International / Plan: ISDN Prefix + (Calling & Called) Strip Predot Calling Line ID Presentation: Restricted

999 PT_UK / CSS_GLOBAL (Urgent) Number Type: Subscriber / Plan : ISDN Prefix + (Calling & Called)

9.[1-8]XXXXXXXX PT_UK / CSS_GLOBAL (Not Urgent) Number Type: Subscriber / Plan: ISDN Prefix + (Calling & Called) Strip Predot

9.0[1-8]XXXXXXXXX PT_UK / CSS_GLOBAL (Not Urgent) Number Type: National / Plan: ISDN Prefix + (Calling & Called) Strip Predot

9.00! PT_UK / CSS_GLOBAL (Not Urgent) Number Type: International / Plan: ISDN Prefix + (Calling & Called) Strip Predot

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



Next, create a Called Party Transformation pattern \+.! In PT_HQ_CALLED, and Strip Predot:



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 H.323 gateway, and the SIP Trunk. 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.



Create a CTI Route Point in the CallManager to redirect all incoming calls with no matched extension to BR1 IP Phone 2: (**Note that task 5.1 must be completed before the following steps can be configured) Step 1: Navigate to Device > CTI Route Point and click the Add a New CTI Route Point link. Set the name to Br1_Route_Point, “Device Pool” to “DP_BR1” and “Location” to “LOC_BR1” then click the Save button:

Next, click the Line [1] link:



Step 2: On the Directory Number configuration page set “Directory Number” to “2XXX”. Under the “Call Forward and Pickup Settings” page section set “Forward All” to “2002” and then click the Add button:



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 160Kbps (2x80Kbps) and “LOC_BR2” bandwidth to 72Kbps (3x24Kbps):

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 MOH HQ G.711 G.711 G.729 G.711 BR1 G.711 G.729 G.729 BR2 G.711 G.729 MOH 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, BR1 and BR2 gateway) depending on their site, set the “Location” field to “LOC_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” field is 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 > Service Parameters and select “177.1.10.10” as the “Server” and “IP Voice Media Streaming Application” as the “Service”. Set “Supported MoH Codecs” to “G711mulaw” and “G729AnnexA” (**Note that you must use Control + Click to select both Codecs)

Step 3: Navigate to Media Resource > Music on Hold Server and then click the Find button. For each of the MoH Servers listed, set the “Device Pool” to “DP_MOH” and “Location” to “HUB_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 “Increment Multicast on IP Address”, and then click the Update button:

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



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 the Save button:

Next, click the Related Link for the Music On Hold Server Configuration. Set the Maximum Hops 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.11 ip pim dense-mode ! interface FastEthernet 0/0.10 ip pim dense-mode ! interface Serial 0/0/1:0.1 ip pim dense-mode



R2: ip multicast-routing ! interface Vlan 11 ip pim dense-mode ! interface Serial 0/0/1:0.1 ip pim dense-mode ! interface Loopback0 ip pim dense-mode R3: ip multicast-routing ! interface FastEthernet 0/0.11 ip pim dense-mode ! interface Serial 1/1:0.1 ip pim dense-mode Perform the following steps to add the DSP resources from R1 as a conference bridge for the CUCM cluster: 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 ! ! The number of xcoding sessions ! 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_BR1 MRG_CFB_HW MRG_MOH_SUB_MCAST MRG_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.

Task 7.1 Step 1: Call Routing > Class of Control > Partition then click the Add a New Partition link. Name the new partition as “PT_MANAGER” and click the Insert button. Step 2: Navigate to Route Plan > Class of Control > Calling Search Space and click the Add a New Calling Search Space link. Fill in the “Calling Search Space” as “CSS_MGR” and move the “PT_MANAGER” partition from “Available Partition” to “Selected Partitions” then click the Insert button. Step 3: Navigate to Device > CTI Route Point and click the Add a new CTI Route Point link. Enter “RP_IPMA” for the “Device Name”, “DP_HQ” for the “Device Pool”, set the “Calling Search Space” field to “CSS_MGR”, set the “Location” field to “HUB_NONE” and then click the Save button.

Step 4: Set the “Directory Number” to “1XXX”, “Partition” to “PT_INTERNAL” and click the Add button.



Step 5: Find the URL value for IPMA Proxy mode service under the “Cisco IP Manager Assistant with Proxy Line support” DocCD section. Navigate to Device > Device Settings > Phone Services and 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 the Publisher CallManager and select “IP Manager Assistant” application. Set the field values per 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 Proxy Mode

“RP_IPMA”

Cisco IPMA Server (Primary) IP Address

“177.1.10.10”

Once completed click the Save button.



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 partition named PT_INTERCOM. Click Save. Step 2: Navigate to Device > Device Settings > Phone Button Template. Select the template corresponding 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 the third button to be a line appearance, instead of a Speed Dial:

Step 3: Navigate to Device > Phone section and locate HQ IP Phone 1 using the Find function. Change the “Softkey Template” field to “Standard Manager”, and the "Button Template" to IMPA Template 3+3:



Step 4: Choose Line 1 of the phone and change the “Partition” field to “PT_MANAGER” then click the Save button. Next, Choose Line 2 and set the Intercom DN number to *1001, choose the 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 in the related links navigation menu. Under “Select a Service” menu choose “IPMA”, click the Continue button then click the Subscribe button, then click Save. Step 6: Navigate to Device > Phone and locate HQ IP Phone 2 using the Find button. Under the device settings ensure the Phone Button Template is set to “"IMPA Template 3+3”. Change the “Softkey Template” to “Standard IPMA Assistant”. Step 7: Choose Line 2 and set the Intercom DN number to *1002, choose the partition created for the 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, set the “Directory Number” to “1011”, and the “Calling Search Space” to “CSS_MGR”. Change “Display (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 then click the Save button. Step 2: Click the Device Association link on the User page. Locate HQ IP Phone 1, check the device 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 Name” and “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 Association link on the User page. Locate HQ IP Phone 2, check the device 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:



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 line settings configured earlier:

Step 3: To install the IPMA applicaton, navigate to Application > Plugins. Click the download icon next to the Cisco Unified CallManager Assistant Console. Once the application has downloaded, 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 you configured previously. Once the application has launched and autheticated, you can test the IPMA configuration, by placing a call from another phone to 1001, HQ Ph2 should ring.

Task 8.1 Perform the following steps in order to enable AAR functionality: Step 1: System > Service Parameters. Select the IP address corresponding to the Publisher CallManager and choose the Cisco CallManager service. Step 2: Change the “Automated Alternate Routing Enable” flag to “True” and click the Save button:



Step 3: Navigate to Call Routing > AAR Group and click the Add a New AAR Group link. Enter “AAR_ALL” as the “AAR Group Name” and click the Save button. No dial prefixes are needed, as global routing is enabled with the Internation Route Pattern \+! Step 4: Navigate to Device > Phone. Select each phone, and set the AAR group. Next, set the AAR Calling Search Space to CSS_GLOBAL. Then click the Line 1 link under the “Directory Numbers”, change the “AAR Group” to “AAR_ALL” then click the Save button. Step 5: Navigate to Device > Gateway and find the device corresponding to R1 MGCP gateway. change the “AAR Group” to “AAR_ALL” then click the Update button. Step 6: Repeat Step 5 for the SIP Trunk corresponding to BR1 gateway. Apply your changes under the Device > Trunk section of the menu. Step 7: Repeat Step 6 for H.323 BR2 gateway. Task 9.1 SW1: mls qos mls qos map cos-dscp 0 8 16 24 34 46 48 54 ! ! ! interface range FastEthernet 0/2 - 3 mls qos trust cos switchport priority extend cos 1 mls qos trust device cisco-phone



SW2: mls qos mls qos map cos-dscp 0 8 16 24 34 46 48 54 ! ! ! interface range FastEthernet 0/1 - 2 mls qos trust cos switchport priority extend cos 1 mls qos trust device cisco-phone ! ! CME uses DSCP 26 for signaling so we need to change this to 24 (CS3) ! It’s not strictly necessary actually, just a good thing to keep in mind ! mls qos map dscp-mutation DSCP26_TO_24 26 to 24 ! ! Uplink ! interface FastEthernet 0/24 mls qos trust dscp mls qos dscp-mutation DSCP26_TO_24 (VoIP gateway marking (MGCP, H.323, SIP) previously configured in the gateway section) Tasks 9.2 - 9.4 R1: class-map VOICE_SIGNALING match ip dscp cs3 ! class-map VOICE_BEARER match ip dscp ef ! ! Policy-maps to implement CBWFQ per VC ! policy-map CBWFQ_BR1 class VOICE_BEARER ! ! Allocate bandwidth for 3xG.711 compressed calls (L3+L2 bandwidth): ! 2 calls per CAC requirement + 1 multicast MoH flow ! Each call is 67,6Kbps of bandwidth per SRND tables ! priority 203 compress header ip rtp class VOICE_SIGNALING bandwidth remaining percent 3 class class-default fair-queue



policy-map CBWFQ_BR2 class VOICE_BEARER ! ! 3 Calls per CAC requirements and 1 multicast data flow ! 4*11,6 Kpbs = 46,4 rounded up to 47 Kpbs ! 11,6Kbps is G.729 cRTP compressed over Frame-Relay ! priority 47 compress header ip rtp class VOICE_SIGNALING no bandwidth bandwidth remaining percent 3 class class-default fair-queue ! ! “Parent” policy-maps to shape PVC traffic ! Set CIR values to RealCIR * 0,95 ! policy-map SHAPE_TO_BR1 class class-default shape average 365000 3650 0 service-policy CBWFQ_BR1 policy-map SHAPE_TO_BR2 class class-default shape average 243000 2430 0 service-policy CBWFQ_BR2 map-class frame-relay DLCI_101 service-policy output SHAPE_TO_BR1 map-class frame-relay DLCI_201 service-policy output SHAPE_TO_BR2 ! ! Fragment size is chosen based on 768Kpbs port speed (10ms delay) ! interface Serial 0/0/1:0 no frame-relay traffic-shaping frame-relay fragment 960 end-to-end ! interface Serial 0/0/1:0.1 frame-relay interface-dlci 101 class DLCI_101 ! interface Serial 0/0/1:0.2 frame-relay interface-dlci 201 class DLCI_201



R2: class-map VOICE_SIGNALING match ip dscp cs3 ! class-map VOICE_BEARER match ip dscp ef ! policy-map CBWFQ_HQ class VOICE_BEARER ! ! Upstream is only 2 voice calls, MoH is only downstream ! priority 136 compress header ip rtp class VOICE_SIGNALING bandwidth remaining percent 3 class class-default fair-queue policy-map SHAPE_TO_HQ class class-default shape average 365000 3650 0 service-policy CBWFQ_HQ map-class frame-relay DLCI_101 service-policy output SHAPE_TO_HQ interface Serial 0/0/1:0 no frame-relay traffic-shaping frame-relay fragment 960 end-to-end ! interface Serial 0/0/1:0.1 frame-relay interface-dlci 101 class DLCI_101 R3: class-map VOICE_SIGNALING match ip dscp cs3 ! class-map VOICE_BEARER match ip dscp ef ! policy-map CBWFQ_HQ class VOICE_BEARER priority 35 compress header ip rtp class VOICE_SIGNALING bandwidth remaining percent 3 class class-default fair-queue



policy-map SHAPE_TO_HQ class class-default shape average 243000 2430 0 service-policy CBWFQ_HQ map-class frame-relay DLCI_201 service-policy output SHAPE_TO_HQ interface Serial 1/1:0 no frame-relay traffic-shaping frame-relay fragment 960 end-to-end ! interface Serial 1/1:0.1 frame-relay interface-dlci 201 class DLCI_201

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 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 Value First 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.



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 Value IP Address “177.1.10.40” Username (Windows) Administrator Password (Windows) cciecisco Username (CUCCX Initilization) Administrator Password (CUCCX Initilization) ciscocisco JTAPI Username/Password jtapi/cisco RMCM 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 Value Number 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.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 > 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 Next button.



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 Value Directory 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 1 - ines3. · task 1.2 r1:! ensure you exclude addresses! before you configure an ios dhcp...

Documents