You are on page 1of 102

CIPT1

Implementing Cisco Unified Communications Manager, Part 1


Version 8.0

Lab Guide
Text Part Number: 97-2867-01

DISCLAIMER WARRANTY: THIS CONTENT IS BEING PROVIDED AS IS. CISCO MAKES AND YOU RECEIVE NO WARRANTIES IN CONNECTION WITH THE CONTENT PROVIDED HEREUNDER, EXPRESS, IMPLIED, STATUTORY OR IN ANY OTHER PROVISION OF THIS CONTENT OR COMMUNICATION BETWEEN CISCO AND YOU. CISCO SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE. This learning product may contain early release content, and while Cisco believes it to be accurate, it falls subject to the disclaimer above.

Lab Guide

2010 Cisco and/or its affiliates. All rights reserved.

Table of Contents
Lab Guide 1
Overview 1 Outline 1 Lab 2-1: Configuring Cisco Unified Communications Manager Initial Settings 2 Activity Objective 2 Visual Objective 2 Required Resources 2 Job Aids 3 Task 1: Eliminate DNS Reliance 3 Task 2: Manage Network and Feature Services 4 Task 3: Configure Cisco Unified Communications Manager to Provide DHCP Services 6 Task 4: Configure Cisco Unified Communications Manager Enterprise and Service Parameters 7 Lab 2-2: Managing User Accounts in Cisco Unified Communications Manager 9 Activity Objective 9 Visual Objective 9 Required Resources 9 Job Aids 10 Task 1: Manage User Accounts by Using Cisco Unified Communications Manager Administration 10 Task 2: Manage User Accounts by Using Cisco Unified Communications Manager BAT 12 Lab 3-1: Implementing IP Phones 15 Activity Objective 15 Visual Objective 15 Required Resources 15 Job Aids 16 Task 1: Configure System Parameters 16 Task 2: Add IP Phones by Using Autoregistration 18 Task 3: Manually Add and Configure an IP Phone 19 Task 4 (Optional): Prepare Cisco Unified Communications Manager BAT for Adding Cisco IP Phones 20 Task 5 (Optional): Insert IP Phones into the Cisco Unified Communications Manager Database by Using Cisco Unified Communications Manager BAT 23 Task 6: Configure Cisco Unified Communications Manager to Support a Third-Party SIP Softphone 24 Task 7 (Optional): Enable Digest Authentication for a Third-Party SIP Softphone 25 Lab 4-1: Implementing PSTN Gateways 27 Activity Objective 27 Visual Objective 27 Required Resources 27 Command List 28 Job Aids 28 Task 1: Configure an MGCP Gateway by Using T1/E1 PRI to the PSTN in Cisco Unified Communications Manager 29 Task 2: Configure a Cisco IOS Gateway for MGCP 30 Task 3: Configure a Route Pattern Towards the MGCP Gateway 32 Task 4: Add an H.323 Gateway in Cisco Unified Communications Manager 33 Lab 4-2: Configuring Cisco Unified Communications Manager Call-Routing Components 34 Activity Objective 34 Visual Objective 34 Required Resources 34 Job Aids 35 Task 1: Configure a Route Plan That Uses Both Gateways and Includes Two Route Groups, a Route List, and Route Pattern 35 Task 2 (Optional): Enable Cisco Unified Communications Manager Dialed Number Analyzer and Use It for Dial Plan Verification 37

Lab 4-3: Implementing Digit Manipulation 39 Activity Objective 39 Visual Objective 39 Required Resources 39 Job Aids 40 Task 1: Configure Cisco Unified Communications Manager to Strip Access Codes That Are Used for Called Numbers on Outgoing Calls 40 Task 2: Configure Cisco Unified Communications Manager to Extend Calling Numbers in Outgoing Calls to Fully Qualified PSTN Numbers 41 Task 3: Configure Cisco Unified Communications Manager to Reduce the Called PSTN Number of Incoming Calls to Directory Numbers 42 Task 4: Configure Cisco Unified Communications Manager to Prefix Access Codes to Calling Numbers on Incoming PSTN Calls 43 Task 5 (Optional): Implement E.164 Plus Dialing and Phone Number Localization 44 Lab 4-4: Implementing Calling Privileges in Cisco Unified Communications Manager 46 Activity Objective 46 Visual Objective 46 Required Resources 46 Job Aids 47 Task 1: Configure Partitions and CSSs 48 Task 2: Implement CoS for Internal Calls 49 Task 3: Implement CoS for Incoming PSTN Calls 50 Task 4: Implement CoS for Outgoing PSTN Calls 51 Task 5 (Optional): Implement Time-of-Day-Based CoS 52 Task 6 (Optional): Implement FACs 54 Lab 4-5: Implementing Call Coverage in Cisco Unified Communications Manager 56 Activity Objective 56 Visual Objective 56 Required Resources 56 Task 1: Create a Line Group and Add Members 57 Task 2: Create a Hunt List and Add Line Groups 58 Task 3: Create a Hunt Pilot Number and Associate It with a Hunt List 58 Task 4: Test Call Distribution 59 Task 5 (Optional): Configure Final Forwarding for Busy and No-Answer Conditions 60 Lab 5-1: Implementing Media Resources 62 Activity Objective 62 Visual Objective 62 Required Resources 62 Command List 63 Task 1: Add a Software Conference Media Resource in Cisco Unified Communications Manager 63 Task 2: Add a Hardware Conference Media Resource 64 Task 3: Configure Meet-Me Conferences in Cisco Unified Communications Manager 66 Task 4: Manage MOH Audio Files 67 Task 5 (Optional): Configure Multicast MOH 69 Task 6 (Optional): Implement Media Resources Access Control 71 Lab 6-1: Configuring Cisco Unified Communications Manager Native Presence 75 Activity Objective 75 Visual Objective 75 Required Resources 75 Task 1: Configure Presence-Enabled Speed Dials 76 Task 2: Implement Presence-Enabled Call Lists 77 Task 3 (Optional): Configure Presence Policies 77

ii

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Lab 6-2: Configuring Cisco Unified Mobility Activity Objective Visual Objective Required Resources Task 1: Add the Mobility Softkey to IP Phones Task 2: Associate an End User Account with the IP Phone and Enable the Use of Mobility Task 3: Configure Remote Destination Profiles and Remote Destinations Task 4: Configure Ring Schedules and Access Lists for Remote Destinations Task 5: Enable MVA Task 6: Configure Cisco Unified Mobility Media Resources Task 7: Configure the Cisco IOS Gateway for Cisco Unified Mobility Answer Key Lab 2-1: Configuring Cisco Unified Communications Manager Initial Settings Lab 2-2: Managing User Accounts in Cisco Unified Communications Manager Lab 3-1: Implementing IP Phones Lab 4-1: Implementing PSTN Gateways Lab 4-2: Configuring Cisco Unified Communications Manager Call-Routing Components Lab 4-3: Implementing Digit Manipulation Lab 4-4: Implementing Calling Privileges in Cisco Unified Communications Manager Lab 4-5: Implementing Call Coverage in Cisco Unified Communications Manager Lab 5-1: Implementing Media Resources Lab 6-1: Configuring Cisco Unified Communications Manager Native Presence Lab 6-2: Configuring Cisco Unified Mobility

79 79 79 79 80 80 81 84 85 86 87 92 92 92 92 92 93 93 93 93 93 95 95

2010 Cisco Systems, Inc.

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

iii

iv

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

CIPT1

Lab Guide
Overview
This guide presents the instructions and other information concerning the lab activities for this course. You can find the solutions in the lab activity Answer Key.

Outline
This guide includes these activities:

Lab 2-1: Configuring Cisco Unified Communications Manager Initial Settings Lab 2-2: Managing User Accounts in Cisco Unified Communications Manager Lab 3-1: Implementing IP Phones Lab 4-1: Implementing PSTN Gateways Lab 4-2: Configuring Cisco Unified Communications Manager Call-Routing Components Lab 4-3: Implementing Digit Manipulation Lab 4-4: Implementing Calling Privileges in Cisco Unified Communications Manager Lab 4-5: Implementing Call Coverage in Cisco Unified Communications Manager Lab 5-1: Implementing Media Resources Lab 6-1: Configuring Cisco Unified Communications Manager Native Presence Lab 6-2: Configuring Cisco Unified Mobility Answer Key

Lab 2-1: Configuring Cisco Unified Communications Manager Initial Settings


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure Cisco Unified Communications Manager initial settings to activate services. You will use the Cisco Unified Communications Manager IP address rather than its hostname. After completing this activity, you will be able to meet these objectives:

Change the hostname of Cisco Unified Communications Manager into its IP address Activate and manage required services Configure Cisco Unified Communications Manager to provide DHCP services Configure Cisco Unified Communications Manager enterprise and service parameters

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 2-1: Configuring Cisco Unified Communications Manager Initial Settings


Phone1-x Phone2-x Phone3-x

D HCP

DH CP

D HCP

10.x.2.0/24 PC-x HQ-x


DH CP .2 .101

10.x.3.0/24

. 101 .1 01

10.x.1.0/24

CUCM2-x

Configure initial settings and enable DHCP services

.1

CUCM1-x

2010 Cisco S ystems , I nc. A ll rights res erv ed.

CIPT 1 v 8. 04

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC Cisco IP phones

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Lab Devices and Their Roles


Device CUCM1-x CUCM2-x PC-x Device Role in the Activity Cisco Unified Communications Manager publisher Cisco Unified Communications Manager subscriber Student computer with web browser

Use the credentials in the table to log in to the lab devices that require authentication. Credentials for CUCM1-x Application Access
Device Cisco Unified Communications Manager Administration GUI Cisco Unified Communications Manager Serviceability GUI Username and Password cucmadmin cucmpass1 cucmadmin cucmpass1 Access https://10.x.1.1/ccmadmin https://10.x.1.1/ccmservice

Job Aids
This job aid is available to help you complete the lab activity. The addressing of lab devices uses the IP allocation scheme that is shown in the table. IP Allocation Scheme
Parameter Value 10.x.1.0/24 10.x.3.0/24 HQ-x: Node address .101 (for all networks) 10.x.1.1/24 10.x.1.2/24 10.x.3.1/24

Voice server network Data network Default gateways CUCM1-x CUCM2-x PC-x

Task 1: Eliminate DNS Reliance


In this task, you will eliminate the need for DNS, by changing from DNS names to IP addresses.

Activity Procedure
Complete these steps:
Step 1

From PC-x, access Cisco Unified Communications Manager Administration using the information provided in the Credentials for CUCM1-x Application Access table. Go to System > Server and click Find to list all the servers in your cluster. Click CUCM1-x and change the Host Name/IP Address field from CUCM1-x to 10.x.1.1. Add a description for your server. Enter Publisher in the Description field. Click Save and then click OK.
Lab Guide 3

Step 2 Step 3 Step 4 Step 5


2010 Cisco Systems, Inc.

Note

The subscriber has already been configured with its IP address during the installation procedure, because installation requires the subscriber to be added as a server before installing it.

Step 6 Step 7

Under System > Enterprise Parameters, determine whether the phone URLs still include hostnames (CUCM1-x). Change the hostname part of all phone URLs to the appropriate IP address and click Save (for example change http://CUCM1-x:8080/ccmcip/authenticate.jsp to http://10.x.1.1:8080/ccmcip/authenticate.jsp).

Activity Verification
You have completed this task when you attain these results:

IP addresses are used for the server names. Go to System > Server and click Find to list all the servers in your cluster. Both the publisher and subscriber servers should be listed, with an IP address in the Host Name/IP Address column and with a Description. Go to System > Enterprise Parameters. In the Phone URL Parameters pane, all URLs should contain the IP address of the publisher server (10.x.1.1, where x is your pod number).

IP addresses are used in phone URLs.

Task 2: Manage Network and Feature Services


In this task, you will activate the minimum services that are required by Cisco Unified Communications Manager to serve Cisco IP phones.

Activity Procedure
Complete these steps: Configure Cisco Unified Communications Manager Servers Step 1 From PC-x, access Cisco Unified Communications Manager Administration.
Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

Go to System > Cisco Unified CM and click Find. Click the CM_CUCM1-x name to enter the Cisco Unified CM Configuration window. Change the automatically generated Cisco Unified Communications Manager name to CUCM1-x (where x is your pod number). In the Description field, enter Publisher. Click Save and then click OK. Go back through the Related Links menu to Back To Find/List and repeat the last three steps for the subscriber CM_10.x.1.2. Rename the subscriber to CUCM2-x and enter Subscriber for the description.

Activate Cisco Unified Communications Manager Services Step 8 From PC-x, access Cisco Unified Serviceability.
Step 9 Step 10
4

Go to Tools > Service Activation. At the Select Server page, choose 10.x.1.1 and then click Go.
2010 Cisco Systems, Inc.

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Note

The DHCP service can be activated on multiple servers. You will enable the DHCP service at the subscriber in a later task.

Step 11

From the list of services, check Cisco CallManager, Cisco TFTP, and Cisco DHCP Monitor Service.
You will need the Cisco DHCP Monitor Service to perform the next task in this lab.

Note Step 12

Click Save to activate these services. A pop-up window appears and informs you that service activation will take a while. Confirm by clicking OK, and then wait until the Status (on top-left corner of the page) changes from Ready to Update Operation Successful. Using the related links or Tools > Control CenterFeature Services, go to the Control Center for feature services. Verify that the Cisco CallManager, Cisco TFTP, and Cisco DHCP Monitor Service services are started and activated. Repeat the previous steps to activate the Cisco CallManager service on the subscriber. This service is the only one that you will activate on the subscriber. Verify that the Cisco CallManager service is running on the subscriber.

Step 13 Step 14 Step 15 Step 16

Activity Verification
You have completed this task when you attain these results:

Verify that the new names are configured. Go to System > Cisco Unified CM and click Find. In the result list, both Cisco Unified Communications Manager servers should be listed with the new configured names:

CUCM1-x CUCM2-x

Verify that all required services are started. In the Cisco Unified Serviceability, go to Tools > Control CenterFeature Services. Make sure that the Cisco CallManager, Cisco TFTP, and Cisco DHCP Monitor Service services are shown as started services on the publisher. Make sure that the Cisco CallManager service is shown as a started service on the subscriber.

2010 Cisco Systems, Inc.

Lab Guide

Task 3: Configure Cisco Unified Communications Manager to Provide DHCP Services


In this task, you will configure Cisco Unified Communications Manager to assign IP addresses to IP phones via DHCP.

Activity Procedure
Complete these steps:
Step 1 Step 2

In Cisco Unified Communications Manager Administration, navigate to System > DHCP > DHCP Server and click the Add New button. In the DHCP Server Configuration window, enter the following parameters:

Host Server: 10.x.1.1 Primary TFTP Server IP Address (Option 150): 10.x.1.1 Keep the default values for all other parameters.

Step 3 Step 4 Step 5

Verify the entered parameters and click Save. Navigate to System > DHCP > DHCP Subnet and click Add New. In the DHCP Subnet Configuration window, choose the newly created DHCP server and enter the following parameters:

Subnet IPv4 Address: 10.x.2.0 Primary Start IPv4 Address: 10.x.2.11 Primary End IPv4 Address: 10.x.2.19 Primary Router IPv4 Address: 10.x.2.101 IPv4 Subnet Mask: 255.255.255.0

Note

By specifying option 150 at the DHCP server, you made the configured value the default value for all DHCP subnets. Therefore, this parameter does not need to be set again during the DHCP subnet configuration.

Step 6 Step 7

Verify the entered parameters, and then click Save. Open a Telnet session to reach your HQ-x router (IP address 10.x.250.101). Log in and change to enable mode. The login password and enable secret password are cisco. In global configuration mode, enter the following commands:
interface ... ip helper 10.x.1.1

Step 8

Note

Use the Ethernet interface that connects to the HQ-x Phones network. This is the interface with IP address 10.x.2.101.

Step 9

Save the configuration to NVRAM.

Activity Verification
You have completed this task when you attain these results:

The DHCP server is configured.


2010 Cisco Systems, Inc.

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

The DHCP subnet is configured. The HQ-x router is configured to act as a DHCP relay at the Phones network.

Further verification, to verify that IP phones obtain an IP address from the Cisco Unified Communications Manager publisher, is performed in Lab 3-1.

Task 4: Configure Cisco Unified Communications Manager Enterprise and Service Parameters
In this task, you will enable the dependency records and verify the automatically created URLs. You will also enable the CDR and CMR) service parameters.

Activity Procedure
Complete these steps: Configure Enterprise Parameters Step 1 Navigate to System > Enterprise Parameters.
Step 2 Step 3 Note

In the CCMAdmin Parameters pane, activate the Enable Dependency Records parameter by setting the value to True. Click OK in the pop-up window, and then click Save.
Dependency records help you to determine which records in the database use other records. For example, you can determine which devices (such as CTI route points or phones) use a particular CSS. If you need to delete a record from Cisco Unified Communications Manager, you can use dependency records to show which records are associated with the record that you want to delete. You then can reconfigure those records so that they are associated with a different record.

Configure Service Parameters Step 4 Navigate to System > Service Parameters and choose the publisher server. Wait for the window to refresh and then choose the Cisco CallManager service from the drop-down list.
Step 5 Note

Set the CDR Enabled Flag value to True in the System parameters.
The CDR Enabled Flag parameter determines whether CDRs are generated. Valid values specify True (CDRs are generated) or False (CDRs are not generated).

Step 6 Step 7

Set the CDR Log Calls with Zero Duration Flag to True in the System parameters. Set the CMR parameter Call Diagnostics Enabled value to Enabled Only When CDR Enabled Flag is True in the Clusterwide Parameters (DeviceGeneral).
The Call Diagnostics Enabled parameter determines whether CMRsalso called diagnostic recordsare generated. Generating CMRs without corresponding CDRs can cause uncontrolled disk-space consumption. Therefore, you should always enable CDRs when CMRs are enabled. If you choose Enabled Only When CDR Enabled Flag is True and the CDR Enabled Flag service parameter is set to False, no CMRs will be generated.

Note

Step 8
2010 Cisco Systems, Inc.

Save the changes.


Lab Guide 7

Step 9 Note

Repeat Steps 5 and 6 for the subscriber server and save the changes.
There is no need to repeat Step 7 for the subscriber server because the parameter that is changed in Step 7 is a clusterwide parameter and is automatically applied to all servers.

Activity Verification
You have completed this task when you attain these results:

The Dependency Records parameter is enabled. In System > Enterprise Parameters, verify that the Enable Dependency Records parameter is set to True. The CDR and CMR parameters are enabled. Go to System > Service Parameters and choose the publisher server. Wait for the window to refresh and then choose the Cisco CallManager service from the dropdown list. The CDR Enabled Flag and the CDR Log Calls with Zero Duration Flag are set to True, and the CMR parameter Call Diagnostics Enabled is set to Enabled Only When CDR Enabled Flag Is True. Repeat the previous steps at the subscriber.

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Lab 2-2: Managing User Accounts in Cisco Unified Communications Manager


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will practice how to manage user accounts. You will add administrators with different administrative privileges. After completing this activity, you will be able to meet these objectives:

Manage user accounts by using the administration GUI Manage user accounts by using Cisco Unified Communications Manager BAT

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 2-2: Managing User Accounts in Cisco Unified Communications Manager


Phone1-x Phone2-x Phone3-x

DHCP

DHCP

DHCP

10.x.2.0/24 PC-x HQ-x .101


DHCP .2

10.x.3.0/24

.101 .101

10.x.1.0/24

CUCM2-x

.1

Locally configure and manage user accounts

CUCM1-x

2010 Cisco Systems, Inc. All rights reserved.

CIPT1 v8.05

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC

2010 Cisco Systems, Inc.

Lab Guide

Lab Devices and Their Roles


Device CUCM1-x PC-x Device Role in the Activity Cisco Unified Communications Manager Student computer with web browser

Use the credentials in the table to log in to the lab devices that require authentication. Credentials for CUCM1-x Application Access
Device Cisco Unified Communications Manager Administration GUI Username and Password cucmadmin cucmpass1 Access https://10.x.1.1/ccmadmin

Job Aids
This job aid is available to help you complete the lab activity. The addressing of lab devices uses the IP allocation scheme that is shown in the table. IP Allocation Scheme
Parameter Value 10.x.1.0/24 10.x.3.0/24 HQ-x: Node address .101 (for all networks) 10.x.1.1/24 10.x.1.2/24 10.x.1.9/24 DHCP assigned (10.x.3.0/24)

Voice server network Data network Default gateways CUCM1-x CUCM2-x AD-x PC-x

Task 1: Manage User Accounts by Using Cisco Unified Communications Manager Administration
In this task, you will create two end-user accounts for two administrators. One administrator should have full access; the other should have read-only access.

Activity Procedure
Complete these steps: Add New User Through Cisco Unified Communications Manager Administration In Cisco Unified Communications Manager, configure a user:
Step 1 Step 2 Step 3

From PC-x, access Cisco Unified Communications Manager Administration. Go to User Management > End User and click Add New. Configure a user with the attributes that follow, and save the newly created account by clicking Save at the bottom of the page or the Save symbol at the top of the End User Configuration window.

User ID: User1


2010 Cisco Systems, Inc.

10

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Step 4

Password: password PIN: 54321 Last Name: Phone1 First Name: User1 User ID: User2 Password: password PIN: 12345 Last Name: Phone2 First Name: User2

Click Add New again and add a second user with these attributes:

Step 5

In User Management > End User, verify that the two end users, User1 and User2, are configured in Cisco Unified Communications Manager Administration.

Assign Access Rights to Users You can define different access rights to different users:
Step 6

The first user, User1, is assigned the Standard CCM Super Users access rights. Click the User ID in the Find and List Users list to open the End User Configuration window. Click Add to User Group in the Permissions Information box on the bottom of the page. In the pop-up window, click Find. Choose the Standard CCM Super Users parameter from the resulting list, and click Add Selected. The selected parameter is visible in the Groups box. In the End User Configuration window, click Save. The status changes to Update Successful. Go back to the Find and List Users list. The second user, User2, is assigned Standard CCM Read Only access rights. Go to the Permissions Information box in the End User Configuration window and click Add to User Group. In the pop-up window, click Find. Choose the Standard CCM Read Only parameter from the resulting list, and click Add Selected. The selected parameter is visible in the Groups box. Click Save. On the top of the page, in the right corner, click the Logout link to log out the cucmadmin user. On the Cisco Unified Communications Manager Administration login page, log in as User1 and access some administrator menus. Go to User Management > End User and verify that the Add and Delete buttons are shown. Click the Logout link to log out User1. On the Cisco Unified Communications Manager Administration login page, log in as User2 and access some administrator menus. Go to User Management > End User and verify that User2 has only read access rights (no buttons to add or delete users are shown).
Lab Guide 11

Step 7 Step 8 Step 9 Step 10 Step 11

Step 12 Step 13 Step 14 Step 15 Step 16

Step 17 Step 18

2010 Cisco Systems, Inc.

Step 19

Log in as User1 again and navigate to the End User menus. Click Find and verify that two users are configured and that you can see the information that is offered on the Find page. Click User1 and change the password to cisco and the PIN to 12345.

Step 20

Activity Verification
You have completed this task when you attain these results:

The first end user is assigned to the standard group Standard CCM Super Users. Navigate to User Management > End User. Select the user, enter the End User Configuration window and go to the Permissions Information box. Verify that Standard CCM Super Users is assigned to the user. In the User Management > End User window, enter the End User Configuration window and go to the Permissions Information box. Verify that Standard CCM Read Only is assigned to the user.

The second end user is assigned to the standard group Standard CCM Read Only.

When logging in with the first username, you have full access to Cisco Unified Communications Manager Administration. When logging in with the second username, you have read-only access to Cisco Unified Communications Manager Administration. You were able to change the password of the newly created users when you were logged in as the first end-user (User1). Navigate to User Management > End User and choose User1. In the User Configuration window, change the password and PIN.

Task 2: Manage User Accounts by Using Cisco Unified Communications Manager BAT
In this task, you will use Cisco Unified Communications Manager BAT to add users and you will configure user templates to assign rights to users.

Activity Procedure
Complete these steps: Activate the Bulk Provisioning Service The Bulk Provisioning Service must be activated to work with Cisco Unified Communications Manager BAT.
Step 1 Step 2 Step 3

In the Cisco Unified Serviceability window, navigate to Tools > Service Activation. In the Service drop-down box, choose the publisher server 10.x.1.1. In the Database and Admin Services area, activate the Cisco Bulk Provisioning Service and click Save. The window refreshes, and the Activation Status corresponding to Bulk Provisioning Service displays Activated.
The Cisco Bulk Provisioning Service can be activated only on the publisher server.

Note

12

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Create New Users with the bat.xlt File After you download the bat.xlt file, you can enter user information in the file. The data will be exported to a .csv file and imported in Cisco Unified Communications Manager through Cisco Unified Communications Manager BAT.
Step 4 Step 5 Step 6

Log in to Cisco Unified Communications Manager Administration, navigate to Bulk Administration > Upload/Download Files, and click Find. Click the check box for the bat.xlt file and click Download Selected. Download the Cisco Unified Communications Manager BAT spreadsheet to the C directory and open the bat.xlt file. If prompted, click Enable Macros to use the spreadsheet capabilities.
The bat.xlt file will be automatically renamed at download. The new filename includes the Cisco Unified Communications Manager Version; for example, bat_8.0.1.10000-40.xlt.

Note

Step 7 Step 8

Click the Users tab at the bottom of the spreadsheet. Complete all mandatory fields in each row, providing the following information:

First Name: User3 Last Name: Phone3 UserID: User3 Password: cisco PIN: 12345 First Name: User4 Last Name: Phone4 UserID: User4 Password: cisco PIN: 12345

Step 9

Provide the following information for a second user:


Step 10 Step 11

Scroll to the right and click Export to BAT Format to transfer the data from the bat.xlt spreadsheet into a CSV-formatted data file. Click OK at the pop-up window. The system saves the file to C:\XLSDataFiles\. The filename is: Users-<timestamp>.txt.
If you enter a comma in one of the fields, bat.xlt encloses that field entry in double quotes when you export to CSV format. If you enter a blank row in the spreadsheet, the system treats the empty row as the end of the file. Data that is entered after a blank line is not converted to CSV format.

Note

Add a New User Template in Cisco Unified Communications Manager User templates are used to define common features for end users.
Step 12 Step 13

Navigate to Bulk Administration > Users > User Template and click Add New. In the User Template Configuration window, enter the following parameters, and then click Save:

2010 Cisco Systems, Inc.

Lab Guide

13

User Template Name: CIPT_Users Check the Default Password to User ID check box. User Locale: English, United States User Group: Standard CCM End Users

Insert New Users in Cisco Unified Communications Manager Through Bulk Administration Menu The newly created .csv file will be imported in Cisco Unified Communications Manager through the Bulk Administration menu.
Step 14 Step 15 Step 16 Step 17 Step 18 Step 19 Step 20 Step 21 Step 22 Step 23 Step 24 Step 25

Go to Bulk Administration > Upload/Download Files. Click Add New. In the File text box, click Browse and locate the file C:\XLSDataFiles\Users<timestamp>.txt. In the Select the Target drop-down box, choose Users. In the Select Transaction Type drop-down box, choose Insert Users. Click Save. The status displays that the upload is successful. Navigate to Bulk Administration > Users > Insert Users. In the File Name field, choose the CSV data file that you created for this bulk transaction (Users-<timestamp>.txt). Choose the user template (CIPT_Users) that you created, from the User Template Name drop-down box. In the Job Information area, enter as Job Description CIPT1 Insert User and click the Run Immediately radio button. Click Submit to create the job for inserting the user records. The Status should display that adding the job was successful and that the job request is submitted. Use the Job Scheduler, in Bulk Administration > Job Scheduler, to see the status of your job.

Verify Added Users in Cisco Unified Communications Manager Step 26 Navigate to User Management > End User and click Find.
Step 27 Step 28

The two newly created users, User3 and User4, should appear in the user list. Browse to https://10.x.1.1/ccmuser and log in with users User3 and User4, using the defined password cisco.
You will be prompted to change the password. You can change the password to the same password that was initially configured: cisco.

Note

Activity Verification
You have completed this task when you attain this result:

The two new users, User3 and User4, appear in the user list. Navigate to User > End User and click the Find button.

14

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Lab 3-1: Implementing IP Phones


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will manually add IP phones to Cisco Unified Communications Manager, by using Cisco Unified Communications Manager BAT and autoregistration. Further, you will harden IP phones by disabling web access and GARP, and by blocking access to the voice VLAN. After completing this activity, you will be able to meet these objectives:

Configure system parameters, including the Cisco Unified Communications Manager group, and device pools, to prepare the Cisco Unified Communications Manager cluster to autoregister IP phones Add IP phones to the Cisco Unified Communications Manager database by using autoregistration Use Cisco Unified Communications Manager BAT to add IP phones to Cisco Unified Communications Manager Manually configure an IP phone and directory number in Cisco Unified Communications Manager Configure Cisco Unified Communications Manager to support a third-party SIP phone

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 3-1: Implementing IP Phones


Phone1-x Phone2-x Phone3-x

Install SIP freeware IP phone at PC-x

DHCP

DHCP

DHCP

10.x.2.0/24 PC-x HQ-x .101


DHCP .2

10.x.3.0/24

.101 .101

10.x.1.0/24

CUCM2-x

.1

Add IP phones in Cisco Unified Communication Manager: Using autoregistration Using Cisco Unified Communications Manager BAT Using GUI (manually)

CUCM1-x

2010 Cisco Systems, Inc. All rights reserved.

CIPT1 v8.06

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster


Lab Guide 15

2010 Cisco Systems, Inc.

Student PC with X-Lite third-party freeware SIP softphone Cisco IP phones

Job Aids
These job aids are available to help you complete the lab activity. DHCP Addressing and Subnet Information for Cisco Unified Communications Manager Server
DHCP Server Subnet IP Address Primary Start IP Address End IP Address Primary Router IP Address Subnet Mask Primary TFTP Server (Option 150) 10.x.1.1

CUCM1-x (10.x.1.1)

10.x.2.0

10.x.2.11

10.x.2.20

10.x.2.101

255.255.25 5.0

Cisco Unified Communications Manager Configuration


Cisco Unified Communications Manager Name CUCM1-x IP Address Function Auto-Registration Directory Number Range 20012002

10.x.1.1

Publisher

Directory Numbers
Device Phone1-x Phone2-x Phone3-x Directory Number 2001 2002 2003

IP Allocation Scheme
Parameter Value 10.x.1.0/24 10.x.3.0/24 HQ-x: Node address .101 (for all networks) 10.x.1.1/24 DHCP assigned (10.x.3.0/24)

Voice server network Data network Default gateways CUCM1-x PC-x

Task 1: Configure System Parameters


In this task, you will prepare the Cisco Unified Communications Manager server for loadsharing and redundancy by configuring different device pools that refer to different Cisco Unified Communications Manager groups. Each group will include both servers, but the priority of the servers will be different in the groups.

16

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Activity Procedure
Complete these steps: Cisco Unified Communications Manager Groups In this section, you will update the default Cisco Unified Communications Manager group to use the publisher as first choice and the subscriber as second choice. You will add another Cisco Unified Communications Manager group, with the subscriber as first choice and the publisher as second choice.
Step 1 Step 2 Step 3

Navigate to System > Cisco Unified CM Group and click Find. Choose Default from the list that is displayed. In the Cisco Communications Manager Group Members area, the publisher (CUCM1-x) should already be in the Selected Cisco Communications Managers pane. Highlight the subscriber (CUCM2-x) in the Available Cisco Communications Manager pane. Use the arrow between the two boxes to move the subscriber server to the Selected Cisco Communications Manager pane. Use the Up arrow and Down arrows to place the publisher Cisco Unified Communications Manager at the top of the list, making it the primary Cisco Unified Communications Manager for the group. Click Save. You might be notified about the reset of devices. Click OK if a pop-up window appears. Click Add New or Copy and repeat the previous procedure to create a second group that is called SubPub, which has the two servers that are listed in reverse order (CUCM2-x before CUCM1-x). Verify that both groups are shown in the Find and List Cisco Unified CM Groups page.

Step 4

Step 5 Step 6

Step 7

Configure Device Pools In this section, you will create device pools that are named to reflect their Cisco Unified Communications Manager group. One device pool is named Default because it uses the default Cisco Unified Communications Manager group. The other device pool is called SubPub because it uses the SubPub Cisco Unified Communications Manager group.
Step 8 Step 9 Step 10

Navigate to System > Device Pool and click Find. Click Default in the list shown. Verify that these characteristics are selected:

Cisco Unified Communications Manager Group: Default Date/Time Group: CMLocal (use the date, time, and time zone of the Cisco Unified Communications Manager server) Region: Default SRST Reference: Disable

Step 11 Step 12

Click Copy. Change the device pool name to SubPub and the Cisco Unified Communications Manager Group to SubPub. Leave all other parameters at the displayed value and click Save.

2010 Cisco Systems, Inc.

Lab Guide

17

Activity Verification
You have completed this task when you attain these results:

There are two Cisco Unified Communications Manager groups. Both include both servers (in different order). There are two device pools. Each one uses a different Cisco Unified Communications Manager group.

Task 2: Add IP Phones by Using Autoregistration


In this task, you will configure Cisco Unified Communications Manager to automatically add new phones by using autoregistration.

Activity Procedure
Complete these steps: Cisco Unified Communications Manager Configuration Step 1 To watch the registration process per phone, unplug the Ethernet cable from Phone2x and Phone3-x. Keep Phone1-x (the phone to which PC-x is connected) plugged in.
Step 2 Step 3 Step 4

Go to System > Cisco Unified CM and click Find. In the list that is shown, choose publisher server CUCM1-x. First enter 2002 for the ending directory number and then 2001 for the starting directory number in the Auto-Registration Information area. After you leave the ending directory number field (for example, by using the Tab key) the system will automatically uncheck the Auto-Registration Disabled on This Cisco Unified Communications Manager check box. Click Save and Apply Config.

Step 5

Register IP Phones by Autoregistration Step 6 Reset your IP phone Phone1-x.


Step 7 Step 8

Observe as the IP phone cycles through the registration process. When the IP phone has successfully registered, it will display the date, time, and directory number. On the registered IP phone, press the Settings button, and then enter 3 on your keypad to view the Device Configuration of the IP phone. Press 1 to view the Cisco Unified Communications Manager settings. The ID of the Cisco Unified Communications Manager that is designated as the primary Cisco Unified Communications Manager is displayed first, with the word Active to the right. The ID of the backup (secondary) Cisco Unified Communications Manager is displayed next, with the word Standby to the right. Plug the Ethernet cable of Phone2-x back into the phone. Repeat Step 8 for Phone2-x. Press the Settings key and then enter 3 on your keypad to view the Device Configuration. Enter 1 on your keypad or press the Select softkey. Again, you will see the primary and secondary Cisco Unified Communications Manager systems and their status. Plug the Ethernet cable of Phone3-x back into the phone. Observe as the IP phone cycles through the registration process. This IP phone should fail to obtain the directory number and should be unable to autoregister

Step 9 Step 10

Step 11 Step 12

18

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

because the autoregistration directory number range was limited to two directory numbers.
Step 13

In Cisco Unified Communications Manager Administration, choose Device > Phone and click Find, without changing any parameters. A list of all registered IP phones is displayed. The device pool and IP address of the Cisco Unified Communications Manager to which the IP phone is currently registered is displayed. The IP address of the Cisco Unified Communications Manager is listed under the Status column. Note that the Description field shows Auto with the directory number, to indicate that a phone is autoregistered. Change the descriptions of the two registered phones to Phone1-x and Phone2-x. If Phone1-x (Cisco Unified IP Phone 7965) does not have directory number 2001 assigned, change the directory number to 2001. If Phone2-x (Cisco Unified IP Phone 7965) does not have directory number 2002 assigned, change the directory number to 2002.

Step 14

Activity Verification
You have completed this task when you attain these results:

The first two Cisco IP phones have directory numbers, and you are able to call from one IP phone to the other. Place a call between Phone1-x and Phone2-x. In the Device > Phone menu, after you click Find, the two newly registered IP phones appear in the list, as described in the activity procedure. The third IP phone attempts to register, but fails with a message that registration is rejected. This rejection happens because autoregistration does not have any directory numbers left to assign to new phones.

Task 3: Manually Add and Configure an IP Phone


In this task, you will manually add a Cisco IP phone (Phone3-x) and assign a directory number. The other phones remain configured through autoregistration.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3 Step 4

In Cisco Unified Communications Manager Administration, navigate to Device > Phone and click Add New. On the new page that is shown, from the Phone Type drop-down menu, choose the actual type of Phone3-x (for example, Cisco 7965). Click Next. On the new page, confirm that the SCCP device protocol is selected and click Next. Obtain the MAC address from Phone3-x. On Phone3-x, click Settings, then choose the Network Configuration, and find the IP phone MAC address at entry 3. Another way to obtain the MAC address is to look on the bar code sticker that is located on the bottom back of the Cisco IP phone. Record the MAC address here: In the Phone Configuration window, enter the Phone3-x parameters:

Step 5

MAC Address: Copy from Step 4 recorded MAC address Description: Phone3-x
Lab Guide 19

2010 Cisco Systems, Inc.

Step 6 Step 7 Step 8 Step 9 Step 10 Step 11

Device Pool: SubPub Phone Button Template: Standard 7965 SCCP Device Security Profile: Cisco 7965Standard SCCP Non-Secure Profile

Click Save. (You will configure additional parameters later in the course.) In the pop-up window that appears, notifying you about the reset, click OK. On the new page, click the Line [1]Add a New DN link to continue to configure the line 1 extension. Enter 2003 in the Directory Number field. Click Save. Use the Related Links to get back to the device-configuration level. Then reset the IP phone. Observe as the IP phone cycles through the registration process. When the IP phone has successfully registered, it will display the date, time, and directory number. Verify that Phone3-x has the subscriber (CUCM2-x) as its primary Cisco Unified Communications Manager (in Active state) and the publisher (CUCM1-x) as its secondary Cisco Unified Communications Manager (in Standby state). Use Cisco Unified Serviceability to stop the Cisco CallManager service at the subscriber. Phone3-x should now show the secondary Cisco Unified Communications Manager (CUCM1-x) as Active because the primary Cisco Unified Communications Manager (CUCM2-x) is not running the Cisco CallManager service. Start the Cisco CallManager service again on the subscriber.

Step 12

Step 13

Activity Verification
You have completed this activity when you attain these results:

Phone3-x registers with directory number 3001. Phone3-x has the subscriber as its primary Cisco Unified Communications Manager and the publisher as its secondary Cisco Unified Communications Manager.

Task 4 (Optional): Prepare Cisco Unified Communications Manager BAT for Adding Cisco IP Phones
In this task, you will prepare Cisco Unified Communications Manager to use Cisco Unified Communications Manager BAT to add IP phones.

Activity Procedure
Complete these steps: Activate the Cisco Bulk Provisioning Service on the Publisher Step 1 In Cisco Unified Serviceability, make sure that the Cisco Bulk Provisioning service is activated on the publisher. Create an IP Phone Template for Use with Cisco Unified Communications Manager BAT Step 2 In Cisco Unified Communications Manager Administration, navigate to Bulk Administration > Phones > Phone Template and click Add New.
Step 3 Step 4

Choose Cisco 7965 for Phone Type and click Next. Leave SCCP as device protocol and click Next.
2010 Cisco Systems, Inc.

20

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Step 5

Create the new phone template with these parameters:


Template Name: BAT-7965 Description: 7965 template Device Pool: SubPub Phone Button Template: Standard 7965 SCCP Device Security Profile: Cisco 7965Standard SCCP Non-Secure Profile

Leave all other settings at their default values and click Save.
Step 6 Step 7 Step 8

Click the Line [1] link in the left column, enter line1 for Line Template Name, and click Save. Highlight BAT-7965 in the Associated Devices pane, and click Edit Device or use the Related Links to get back to the device-configuration level. Click the Line[2] link in the left column, enter line2 for Line Template Name, and click Save.

Create the CSV File Using the Cisco Unified Communications Manager BAT Spreadsheet Step 9 In Cisco Unified Communications Manager Administration, choose Bulk Administration > Upload/Download Files and click Find.
Step 10 Step 11 Step 12 Step 13 Step 14 Step 15

Check the check box next to the bat.xlt file and click Download Selected. In the new dialog window, click Save, and then navigate to the C directory on your local PC. Change the filename in the File Name field to bat7965.xlt and click Save. Wait until the file is downloaded to your local PC. Open the file on your local PC, using Microsoft Excel. On the Phones spreadsheet tab, click the Phones radio button, then click Create File Format. In the new dialog window, highlight the Directory Number in the Line Fields pane, and then click the Right arrow button to move the entry to the Selected Line Fields pane. Click Create, and then click Yes on the pop-up window, to overwrite the existing file. In the Maximum Number of Phone Lines field, enter 2 to create two lines for new IP phones. Then click into any other portion of the spreadsheet to leave the field so that the sheet is updated with the selected number of lines. Check the check box next to the Dummy MAC Address field. On the Phones spreadsheet, enter five new IP phones with the following parameters, and leave the MAC Address column empty.

Step 16 Step 17

Step 18 Step 19

2010 Cisco Systems, Inc.

Lab Guide

21

Description IPPhone6 IPPhone7 IPPhone8 IPPhone9 IPPhone10 Step 20 Step 21 Step 22

Directory Number 1 2006 2007 2008 2009 2010

Directory Number 2 3006 3007 3008 3009 3010

Scroll right and click the Export to BAT Format button. Save the new file with the suggested filename to the suggested folder. You should be notified that the file was successfully exported. Click OK. Exit Microsoft Excel without saving the changes to the .xlt file.

Validate the IP Phone Template and CSV File Step 23 In Cisco Unified Communications Manager Administration, navigate to Bulk Administration > Upload/Download Files and click Add New.
Step 24

Click Browse. In the new dialog window, navigate to C:\XlsDataFiles\, highlight the previously stored file, and then click Open. Doing so will populate the File field on the File Upload Configuration page. Choose Phones from the Select Transaction Type drop-down menu. Choose Insert PhonesSpecific Details from the Select Transaction Type dropdown menu and click Save. Choose Bulk Administration > Phones > Validate phones. From the File Name drop-down menu, choose the previously uploaded CSV file. From the Phone Template Name drop-down menu, choose the BAT-7965 template that you created earlier. Click Submit. Choose Bulk Administration > Job Scheduler and click Find. In the job list that is shown, click the Job Id link that has Validate Specific Phones in the Description column. The job results should display the validation status without errors.

Step 25 Step 26 Step 27 Step 28 Step 29 Step 30 Step 31 Step 32 Step 33

Activity Verification
You have completed this task when you attain this result:

The validation status is Validate Completed, and when you click the Log File Name link, the Result Summary message reads Validate for 5 Phones passed. Validate for 0 Phones failed.
This verification task was part of the lab activity.

Note

22

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Task 5 (Optional): Insert IP Phones into the Cisco Unified Communications Manager Database by Using Cisco Unified Communications Manager BAT
In this task, you will complete the last step in Cisco Unified Communications Manager BAT process by inserting the previously validated IP phones into the Cisco Unified Communications Manager database.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9

Go to Bulk Administration > Phones > Insert Phones. Choose the previously uploaded CSV file from the File Name drop-down menu. Choose BAT-7965 from the Phone Template Name drop-down menu. Check the check box next to Create Dummy MAC Address. Click the Run Immediately radio button. Click Submit. Go to Bulk Administration > Job Scheduler and click Find. If the Status column of the phone insertion job does not show Completed, click Find again. Repeat this step until you see the status Completed. Click the phone insertion Job Id link and make sure that the job has completed successfully. You can also review the log file.

Activity Verification
You have completed this task when you attain these results:

The phones insertion job has completed with success.


This verification step was part of the lab activity.

Note

When you go to Device > Phone and click Find, you see in the list the five new IP phones that you bulk-added. Notice that the telephones that you added with Cisco Unified Communications Manager BAT all start with BAT, followed by a dummy MAC address in the Device Name field. Click one of the device names and view the results. You can customize any of these fields on a per-phone basis.

Cleanup
To prepare for future labs, follow these steps to delete the Cisco Unified Communications Manager telephones that you added by using Cisco Unified Communications Manager BAT.
Step 1 Step 2 Step 3

Go to Device > Phone and click Find. Check the check box next to each bulk-added IP phone (their names start with BAT) and click Delete Selected. Click OK in the pop-up window. Make sure that the only IP phones that remain are the three active IP phones (their names start with SEP).

2010 Cisco Systems, Inc.

Lab Guide

23

Task 6: Configure Cisco Unified Communications Manager to Support a Third-Party SIP Softphone
In this task, you will add a third-party SIP softphone to the Cisco Unified Communications Manager cluster.

Activity Procedure
Complete these steps: Configure Cisco Unified Communications Manager to Support the Third-Party Phone Step 1 In Cisco Unified Communications Manager Administration, go to User Management > End User and list all users.
Step 2 Step 3 Step 4 Step 5

Click User4 and verify its configuration. In Cisco Unified Communications Manager Administration, go to Device > Phone and click Add New. For the Phone Type, choose Third-party SIP Device (Basic) from the drop-down menu. Click Next. On the Phone Configuration page for the third-party SIP device, add a phone with these parameters, and click Save:

MAC Address: Enter any dummy MAC address; third-party SIP phones do not register by MAC address, so the value is irrelevant. Description: Phone4-x Device Pool: Default Phone Button Template: Third-party SIP Device (Basic) SIP Phone Security Profile: Third-party SIP Device BasicStandard SIP Non-Secure Profile SIP Profile: Standard SIP Profile Digest User: User4

Step 6

On the new page, click the Line [1]Add a new DN link to continue to configure the line 1 extension. Enter 2004 in the Directory Number field. Click Save.

Configure the Third-Party Phone to Register with Cisco Unified Communications Manager Step 7 At PC-x, start the X-Lite SIP softphone. If the SIP Accounts window is not automatically shown, right-click in the phone display, choose SIP Account Settings, and click Add.
Step 8

In the Accounts tab, configure these parameters, then click Apply:


Display Name: SIP Phone User Name: 2004 Authorization User Name: User4 Domain: 10.x.1.1 Leave all other settings at default values.

Step 9

Click OK and close the SIP Accounts window.

24

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Step 10

Wait until the third-party SIP phone registers with the Cisco Unified Communications Manager publisher, and then place test calls to other IP phones in your group. In Cisco Unified Communications Manager Administration, go to Device > Phone and click Find. You should see the third-party SIP phone listed, with its status showing Registered. Try to reset the phone from Cisco Unified Communications Manager Administration. The SIP softphone application at the PC is not restarted because only Cisco IP phones can be reset remotely from Cisco Unified Communications Manager Administration.

Step 11

Step 12

Activity Verification
You have completed this task when you attain these results:

On PC-x, the third-party SIP softphone is registered with the Cisco Unified Communications Manager publisher. You can place calls to other phones in your pod from the third-party SIP phone and receive calls from IP phones in your pod. The third-party SIP phone is listed with its IP address as a registered phone in the Find and List Phones page. However, the phone cannot be reset from Cisco Unified Communications Manager Administration. You must manually reboot the phone from the phone.

Task 7 (Optional): Enable Digest Authentication for a ThirdParty SIP Softphone


In this task, you will configure digest authentication to be used for the third-party SIP softphone.

Activity Procedure
Complete these steps: Set a Password at the SIP Phone Step 1 At the SIP softphone (X-Lite), change the configuration to include a password (digestpass).
Step 2 Step 3

Close and reopen the X-Lite application to reset the SIP softphone. Place a call from the SIP softphone. The call should succeed, although you did not set a digest password at Cisco Unified Communications Manager.
This step shows that a digest password that the phone provides is ignored as long as Cisco Unified Communications Manager is not configured to use digest authentication for the thirdparty SIP phone.

Note

Enable Digest Authentication for the Third-Party SIP Phone Step 4 In Cisco Unified Communications Manager Administration, go to System > Security Profile > Phone Security Profile and click Find.
Step 5 Step 6

Click the Copy button to the right of Third-Party SIP Device BasicStandard SIP Non-Secure Profile. Change the name of the profile to Third-Party SIP (Basic) with Digest Authentication. Enter the same text for the description.
Lab Guide 25

2010 Cisco Systems, Inc.

Step 7 Step 8 Step 9 Step 10

Activate the Enable Digest Authentication check box. Then click Save. Go to the phone configuration page of the SIP phone (go to Device > Phone). Change the Device Security Profile to Third-Party SIP (Basic) with Digest Authentication, click Save, and reset the phone. Place a call from the SIP softphone. The call should fail because Cisco Unified Communications Manager now verifies the digest authentication password.
So far you set the digest authentication password only at the third-party SIP phone. The end user in Cisco Unified Communications Manager is not yet configured with a digest authentication password. Therefore, digest authentication fails and the phone cannot register anymore.

Note

Set a Digest Authentication Password at the End User Step 11 Go to User Management > End User and set the digest authentication password at User4 to digestpass. In Cisco Unified Communications Manager, the term for digest password is Digest Credentials.
Step 12 Step 13 Note

At PC-x, close the third-party SIP phone and reopen it to enable the phone to register again. The phone should now be able to register. Place a call from the SIP softphone. The call should succeed.
Cisco Unified Communications Manager is configured to use digest authentication for the third-party SIP phone, and now the digest authentication password that is configured at the phone and at the corresponding end user in Cisco Unified Communications Manager are identical.

Activity Verification
You have completed this task when you attain these results:

The SIP softphone worked with different passwords configured on both ends when Cisco Unified Communications Manager was not configured to use digest authentication. The SIP softphone did not work with different passwords configured on both ends when Cisco Unified Communications Manager was configured to use digest authentication. The SIP softphone worked with the same passwords configured on both ends when Cisco Unified Communications Manager was configured to use digest authentication.

26

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Lab 4-1: Implementing PSTN Gateways


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure Cisco Unified Communications Manager to use a Cisco IOS MGCP gateway as well as an H.323 gateway to connect to the PSTN, by using a direct T1/E1 PRI connection to the PSTN. After completing this activity, you will be able to meet these objectives:

Configure an MGCP gateway using a T1/E1 PRI to connect to the PSTN in Cisco Unified Communications Manager Configure a Cisco IOS gateway for MGCP and obtain MGCP configuration from Cisco Unified Communications Manager Configure an H.323 gateway to connect to the PSTN in Cisco Unified Communications Manager

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 4-1: Implementing PSTN Gateways


Phone1-x Phone2-x Phone3-x

PSTN
DHCP DHCP DHCP

10.x.2.0/24 PC-x HQ-x


DHCP .2 .101

PSTN

10.x.3.0/24

.101 .101

Configure HQ-x as MGCP gateway Configure HQ2-x as H.323 gateway Note: HQ2-x gateway is not physically present.

10.x.1.0/24

CUCM2-x

Add MGCP and H.323 gateways to Cisco Unified Communications Manager


.1 .102

CUCM1-x

HQ2-x

2010 Cisco Systems, Inc. All rights reserved.

CIPT1 v8.07

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC Cisco IP phones

2010 Cisco Systems, Inc.

Lab Guide

27

Cisco IOS MGCP gateway PSTN with PSTN phone

Command List
The table describes the commands that are used in this activity. Cisco IOS Gateway Commands
Command Description Enables you to enter privileged EXEC mode or any other security level that is set by a system administrator Displays information about call setup and teardown of ISDN network connections (Layer 3) between the local router (user side) and the network Enters global configuration mode Specifies the TFTP server from which the MGCP gateway downloads Cisco Unified Communications Manager XML configuration files, and enables download of the configuration Configures the IP address or logical name of the TFTP server from which the XML configuration files are downloaded Enables the MGCP application on the gateway Displays values for MGCP parameters Displays a list of all MGCP endpoints on an MGCP gateway Displays the registration status of the MGCP gateway on its Cisco Unified Communications Manager systems

enable debug isdn q931

configure terminal ccm-manager config

ccm-manager config server

mgcp show mgcp show mgcp endpoint show ccm-manager hosts

Job Aids
These job aids are available to help you complete the lab activity. MGCP Gateway Information
Call Agent 10.x.1.1 Redundant Host 10.x.1.2

28

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Cisco Unified Communications Manager Administration Configuration for MGCP Gateway


Parameter Data HQ-x (where x is your port number) MGCP gateway Default

Domain Name Description Cisco Unified Communications Manager Group Module in Slot 0 Subunit 1 Port Channel Selection Order

NM-4VWIC-MBRD (for ISR routers) VWIC2-1MFT-E1 (depends on actual hardware used) 0/0 (depends on actual hardware used) Top Down

H.323 Gateway Information


Parameter Data HQ2-x (where x is your port number) 10.x.1.102

Hostname HQ2-x IP address

Task 1: Configure an MGCP Gateway by Using T1/E1 PRI to the PSTN in Cisco Unified Communications Manager
In this task, you will configure Cisco Unified Communications Manager to use the MGCP protocol toward the MGCP gateway HQ-x in your cluster.

Activity Procedure
Complete these steps: Add an MGCP Gateway in Cisco Unified Communications Manager Step 1 In Cisco Unified Communications Manager Administration, go to Device > Gateway. On the new page that is shown, click Add New.
Step 2

Choose the gateway platform (for example, Cisco 2811) that is used for Cisco IOS MGCP gateway HQ-x (where x is your cluster number) from the Gateway Type drop-down list and click Next. From the Protocol drop-down list, choose the protocol type MGCP and click Next.

Step 3

Configure an MGCP Gateway in Cisco Unified Communications Manager Step 4 Enter the following parameters in the Gateway Configuration window, then click Save:
Note

Domain Name: HQ-x (where x is your pod number)

The name has to match the hostname of the router and is case-sensitive.

Description: HQ-x MGCP gateway Cisco Unified Communications Manager Group: Default
Lab Guide 29

2010 Cisco Systems, Inc.

Caution

Module in Slot 0: NM-4VWIC-MBRD Global ISDN Switchtype: NI2

These steps are platform-dependent. Ask your instructor to determine the actual hardware that is used for the MGCP gateway. This lab guide is based on the Cisco 2811 router platform with T1/E1 interfaces. You can use the show version, show diag, and show inventory commands to see details about the hardware that is actually used in your lab environment.

Add MGCP Endpoints by Selecting Modules and Voice Interface Cards Step 5 In the Configured Slots, VICs and Endpoints pane, from the Subunit 0 in Slot 0, choose module VWIC2-1MFT-T1E1-T1. Click Save.
Step 6 Step 7 Step 8

Click the port icon 0/0/0 (the far-left endpoint with the question mark). In the next window, from the Device Protocol drop-down list, choose Digital Access PRI, and click Next. In the Gateway Configuration page, choose the following parameters:

Device Pool: Default PRI Protocol Type: NI2 Channel Selection Order: Top Down

Step 9

Save your changes and reset the gateway.

Activity Verification
You have completed this task when you attain this result:

The MGCP gateway appears in the list when you choose Device > Gateway and click Find.

Task 2: Configure a Cisco IOS Gateway for MGCP


In this task, you will enable MGCP on the Cisco IOS MGCP gateway HQ-x.

Activity Procedure
Complete these steps: Access the Cisco IOS MGCP Gateway Step 1 Open a Telnet session to reach your MGCP gateway HQ-x (IP address 10.x.250.101). Log in and change to enable mode. The login password and enable secret password are cisco.
Step 2

In the enable mode, enter the show running-config command. No MGCP commands are currently configured on the gateway.
The Cisco IOS commands shown in this lab exercise depend on the hardware that is used in your class. Ask your instructor for any changes based on the actually used hardware.

Note

Configure the Cisco IOS MGCP Gateway to Use the Configuration Server Method Step 3 In global configuration mode, enter the following commands:
card type t1 0 0 ! network-clock-participate wic 0
30 Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0 2010 Cisco Systems, Inc.

! ccm-manager config server 10.x.1.1 ccm-manager config exit copy running-config startup-config
Note The gateway will now pull its MGCP configuration from the Cisco Unified Communications Manager TFTP server.

Step 4

Enter the show running-config command. You should see more than the two configured MGCP commands.

Reduce the Utilized B-Channels from 24 to 8 Step 5 Disable the configuration server by entering the following command in global configuration mode.
no ccm-manager config
Step 6

In global configuration mode, enter the following commands to shut down the voiceport associated with the T1 PRI.
voice-port 0/0/0:23 shutdown

Step 7

Disable PRI backhauling on the T1 D-channel


interface serial 0/0/0:23 no isdn bind-l3 ccm-manager

Step 8

Remove the autoconfigured pri-group and add a new one.


controller t1 0/0/0 shutdown no pri-group timeslots 1-24 service mgcp pri-group timeslots 1-8 service mgcp no shutdown

Step 9

Re-enable PRI backhauling.


interface serial 0/0/0:23 isdn bind-l3 ccm-manager end

Note

As you deactivated the configuration server feature, the MGCP process at the Cisco IOS gateway is not automatically reset anymore when you reset the gateway in Cisco Unified Communications Manager. You have to manually reset the MGCP process at the Cisco IOS gateway every time after you reset the gateway in Cisco Unified Communications Manager. Enter the command no mgcp command followed by mgcp command in order to reset the MGCP process at the Cisco IOS router.

Activity Verification
You have completed this task when you attain these results:

You can verify that your MGCP gateway has successfully registered to the Cisco Unified Communications Manager by using the show ccm-manager hosts command (Status shows as Registered) and by using the show mgcp endpoint command to check that the MGCPcontrolled T1/E1 PRI endpoint channels are up.

2010 Cisco Systems, Inc.

Lab Guide

31

Verify the MGCP status by using the show mgcp command. The Admin State and the Operational State are Active. Verify that the MGCP gateway and the MGCP endpoints are registered at Cisco Unified Communications Manager: Log in to Cisco Unified Communications Manager Administration. Navigate to Device > Gateway. In the Find Gateways section, choose Show Endpoints and click Find. The status of the MGCP gateway endpoint should be Registered with 10.x.1.1; the gateway IP address should be 10.x.1.101.

Step 1 Step 2 Step 3 Step 4

Task 3: Configure a Route Pattern Towards the MGCP Gateway


In this task, you will configure Cisco Unified Communications Manager to route calls that start with a 9 to the MGCP gateway trunk interface.

Activity Procedure
Complete these steps: Create a Route Pattern in Cisco Unified Communications Manager Step 1 Go to Call Routing > Route/Hunt > Route Pattern, and click Add New.
Step 2

In the Route Pattern Configuration window, enter the following parameters:


Route Pattern: 911 Description: Temporary Route Pattern to PSTN Gateway/Route List: S0/SU0/DS1-0@HQ-x

Step 3 Step 4

Click Save. You are notified by a pop-up window that the authorization code will not be activated. Click OK. You are notified by another pop-up window that changes will reset the gateway. Click OK.

Activity Verification
You have completed this task when you attain these results:

From a Cisco IP phone in your pod, you can successfully reach the PSTN emergency number (part of the simulated PSTN). Specifically, perform these steps: At PC-x, start Cisco IP Communicator. Cisco IP Communicator should display PSTN-Phone-x in the top-right corner of its display. On top of the softkeys, Cisco IP Communicator should display PSTN Phone. If Cisco IP Communicator does not display this information, ask your instructor for help. From one of your Cisco IP phones, place a call to 911. At the PSTN phone (Cisco IP Communicator running on PC-x), accept the call. This call was sent through your HQ-x PSTN gateway.

Step 1 Step 2

Step 3 Step 4

32

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Task 4: Add an H.323 Gateway in Cisco Unified Communications Manager


In this task, you will configure Cisco Unified Communications Manager to use the H.323 protocol toward the H.323 gateway HQ2-x in your cluster.
Note The H.323 gateway will be added to Cisco Unified Communications Manager only to show the necessary configuration steps. The gateway is not physically present. It is only added in Cisco Unified Communications Manager and will be used in the next task to demonstrate that if the preferred gateway (HQ2-x) is not running, a backup gateway (HQ-x) can be used.

Activity Procedure
Complete these steps: Add an H.323 Gateway in Cisco Unified Communications Manager Step 1 In Cisco Unified Communications Manager Administration, go to Device > Gateway, and on the new page that is shown, click Add New.
Step 2

Choose H.323 Gateway from the Gateway Type drop-down list, and click Next.

Configure an H.323 Gateway in Cisco Unified Communications Manager Step 3 Enter the following parameters in the Gateway Configuration window, then click Save:

Device Name: 10.x.1.102 (where x is your pod number) Description: HQ2-x H.323 gateway Device Pool: Default

Activity Verification
You have completed this task when you attain this result:

The H.323 gateway appears in the list when you choose Device > Gateway and click Find.

Cleanup
Delete the route pattern that you created in this lab exercise. In the next lab, you will create route patterns that refer to a route list with redundant gateways. To delete the route pattern, follow these steps:
Step 1 Step 2

Go to Call Routing > Route/Hunt > Route Pattern, and click Find. Select the newly created route pattern 911 and click Delete Selected.

2010 Cisco Systems, Inc.

Lab Guide

33

Lab 4-2: Configuring Cisco Unified Communications Manager Call-Routing Components


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure Cisco Unified Communications Manager for PSTN calls that use multiple gateways. After completing this activity, you will be able to meet these objectives:

Configure a route plan that includes a route group, route list, and route pattern that enables calls to the PSTN Enable Cisco Unified Communications Manager Dialed Number Analyzer and use it for dial plan verification

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 4-2: Configuring Cisco Unified Communications Manager Call-Routing Components


Phone1-x Phone2-x Phone3-x

PSTN
DHCP DHCP DHCP

10.x.2.0/24 PC-x HQ-x


DHCP .2 .101

PSTN

10.x.3.0/24

.101 .101

10.x.1.0/24

CUCM2-x

Configure a route group, route list, and route pattern


.102

.1

HQ2-x CUCM1-x

Use Cisco Unified Communications Manager Dialed Number Analyzer for path verification

2010 Cisco Systems, Inc. All rights reserved.

CIPT1 v8.08

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC Cisco IP Phones

34

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Cisco IOS MGCP gateway PSTN with PSTN phone

Job Aids
This job aid is available to help you complete the lab activity. PSTN Numbering Plan
Pattern 911 XXX XXXX 1 XXX XXX XXXX 011<as many as 14 digits> 1 800 XXX XXXX 1 900 XXX XXXX Destination PSTN phone PSTN phone PSTN phone PSTN phone PSTN phone PSTN phone Description Emergency number Any 7-digit number for PSTN local calls 1 followed by any 10-digit number for PSTN national calls 011 followed by as many as 14 digits for PSTN international calls 1800 followed by 7 digits for PSTN toll free calls 1900 followed by 7 digits for PSTN premium calls

Note

When dialing from the Cisco Unified Communications Manager cluster to the PSTN, a PSTN access code 9 must be prefixed to all PSTN numbers. This PSTN access code should not be sent to the PSTN.

Task 1: Configure a Route Plan That Uses Both Gateways and Includes Two Route Groups, a Route List, and Route Pattern
In this task, you will configure routing to the PSTN, using both configured gateways. You will configure gateway HQ2-x to be preferred over gateway HQ-x.

Activity Procedure
Complete these steps: Create Two Route Groups in Cisco Unified Communications Manager Step 1 Navigate to Call Routing > Route/Hunt > Route Group and click Add New.
Step 2

Enter the following parameter in the Route Group Information window:

Route Group Name: RG_MGCP_GW

Step 3 Step 4 Step 5 Step 6

In the Available Devices field, choose the HQ-x MGCP gateway identifier (S0/SU0/DS1-0@HQ-x) and click Add to Route Group to add the HQ-x gateway. Click Save. Click Add New to add a second Route Group. Enter the following parameter in the Route Group Information window:

Route Group Name: RG_H323_GW

Step 7 Step 8

In the Available Devices field, choose the HQ2-x gateway identifier and click Add to Route Group to add the HQ2-x (10.x.1.102) gateway. Click Save.

2010 Cisco Systems, Inc.

Lab Guide

35

Create a Route List in Cisco Unified Communications Manager Step 9 Navigate to Call Routing > Route/Hunt > Route List, and click Add New.
Step 10

Enter the following parameters in the Route List Configuration window:


Name: RL_HQ_GWs Description: HQ PSTN Gateways Cisco Unified Communications Manager Group: Default

Step 11 Step 12 Step 13 Step 14 Step 15

Click Save. In the updated Route List Configuration page, click Add Route Group in the Route List Member Information pane and choose the RG_MGCP_GW route group. Choose Discard Digits Instruction NANP:PreDot as Called Party Transformation for the RG_MGCP_GW. Click Save. Click OK in the pop-up window. Repeat Steps 12 and 14 for the RG_H323_GW route group, but do not choose any entry in the Discard Digit Instructions for the route group.
Typically the PSTN access code is stripped at the H.323 gateway using Cisco IOS digit manipulation features. Therefore, you have to send PSTN numbers with PSTN access code 9 to the Cisco IOS gateway.

Note

Step 16 Step 17

Change the order of the route groups in the route list so that route group RG_H323_GW is listed before route group RG_MGCP_GW. Click Save. Click OK in the pop-up window.

Create a Route Pattern in Cisco Unified Communications Manager Step 18 Go to Call Routing > Route/Hunt > Route Pattern, and click Add New.
Step 19

In the Route Pattern Configuration window, enter the following parameters:


Route Pattern: 9.!# Description: PSTN Access with # Gateway/Route List: RL_HQ_GWs Discard Digits: <None>

Note Step 20 Step 21 Step 22

Digit manipulation is performed at the route-group level.

Click Save. You are notified by a pop-up window that the authorization code will not be activated. Click OK. You are notified by another pop-up window that changes will reset the gateway. Click OK. Repeat the Steps 16 through 19 to create another route pattern, but enter 9.! as the Route Pattern parameter and enter PSTN Access with Interdigit Timeout as the Description.
You can use the Copy icon to create a copy of the existing route pattern, which you can modify as required.

Note

36

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Activity Verification
You have completed this task when you attain these results:

From a Cisco IP phone in your pod, you can successfully reach a PSTN number using the prefix code 9 (for example, 9-555-7890). When dialing the number, you can either wait for the interdigit timeout to expire or press the # key to instruct Cisco Unified Communications Manager to stop digit collection. Verify that the call is received at PSTN-Phone-x and accept the call at the PSTN phone.

Task 2 (Optional): Enable Cisco Unified Communications Manager Dialed Number Analyzer and Use It for Dial Plan Verification
In this task, you will install Cisco Unified Communications Manager Dialed Number Analyzer and use it to verify that gateway HQ2-x is preferred over gateway HQ-x for calls sent to the PSTN.

Activity Procedure
Complete these steps: Activate Cisco Unified Communications Manager Dialed Number Analyzer Service Step 1 Access Cisco Unified Serviceability, and go to Tools > Service Activation. Choose the publisher server 10.x.1.1 from the Server drop-down list. Click Go.
Note The Cisco Unified Communications Manager Dialed Number Analyzer service must be activated on the publisher server. The service can also be activated on the subscriber server, in case the Cisco Unified Communications Manager Dialed Number Analyzer service on the publisher is unavailable. Activating the service on the subscriber only does not enable the Cisco Unified Communications Manager Dialed Number Analyzer web page.

Step 2 Note Step 3

Choose Cisco Dialed Number Analyzer from the CM Services list, and click Save.
If the service is already activated, the Activation Status displays as Activated.

The service is activated and the Activation Status column displays the status as Activated.

Access Cisco Unified Communications Manager Dialed Number Analyzer Step 4 To access Cisco Unified Communications Manager Dialed Number Analyzer, go to Tools > Dial Number Analyzer in Cisco Unified Serviceability.
Step 5

A pop-up window appears. If you are prompted to enter the username, enter cucmadmin as the user ID and cucmpass1 for password. Click OK. You are now logged in to Cisco Unified Communications Manager Dialed Number Analyzer.
You can also use the URL https://10.x.1.1/dna to access Cisco Unified Communications Manager Dialed Number Analyzer. You do not need to access it from Cisco Unified Serviceability.

Note

Perform a Simple Analysis by Using the Analyzer Window Step 6 Navigate to Analysis > Analyzer.
2010 Cisco Systems, Inc. Lab Guide 37

Step 7 Step 8 Step 9

Enter the calling-party digits 2002 in the Calling Party field. By default, 1000 displays in this field. Enter the digits 9911 (or any other valid PSTN number starting with 9), in the Dialed Digits field. Click Do Analysis to start the analysis. Cisco Unified Communications Manager Dialed Number Analyzer analyzes the dialed digits and displays the results in a new window, the DNA Analysis Output window. In the DNA Analysis Output window, click Expand All. Under Call Flow, at the end of the Route List output section, the gateways are listed in the order in which they are used to route the call.

Step 10

Activity Verification You have completed this task when you attain these results:

In Tools > Control CenterFeature Services, the Cisco Unified Communications Manager Dialed Number Analyzer service is activated and started. From a Cisco IP phone in your pod, you can successfully place a call to the PSTN phone by dialing a valid PSTN number (starting with prefix digit 9). You performed call analysis by using Cisco Unified Communications Manager Dialed Number Analyzer. The output shows that gateway HQ2-x is preferred for calls to the PSTN.
Cisco Unified Communications Manager Dialed Number Analyzer is not aware that the H.323 gateway (HQ2-x) is not running and therefore considers the primary path only. However, because you were able to place the call to the PSTN (using the backup gateway HQ-x), you successfully verified your route list and route group configuration.

Note

Cleanup
Remove the PreDot digit stripping instruction at the Route List for the RG_MGCP_GW Route Group.
Step 1 Step 2 Step 3 Step 4 Step 5

Navigate to Call Routing > Route/Hunt > Route List and click Find. Choose the RL_HQ_GWs route list. Click the RG_MGCP_GW link in the Route List Details field. Set the Discard Digits Instruction to <None>. Click Save, then OK, and then Reset.

38

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Lab 4-3: Implementing Digit Manipulation


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure digit manipulation for PSTN calls. After completing this activity, you will be able to meet these objectives:

Verify Cisco Unified Communications Manager configuration for stripping access codes that are used for called numbers on outgoing calls Configure Cisco Unified Communications Manager to extend calling numbers for outgoing calls to fully qualified PSTN numbers Configure Cisco Unified Communications Manager to shorten the called number of incoming calls to directory numbers Configure Cisco Unified Communications Manager to prefix an access code to calling numbers on incoming calls Implement E.164 Plus dialing and phone number localization

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 4-3: Implementing Digit Manipulation


Phone1-x Phone2-x Phone3-x

PSTN
DHCP DHCP DHCP

10.x.2.0/24 PC-x HQ-x


DHCP .2 .101

PSTN

10.x.3.0/24

.101 .101

Allow outbound PSTN calls to be placed to numbers in + format Remove PSTN access code 9 from called number of outbound PSTN calls Change calling number of outbound PSTN calls from internally used DNs (2XXX) to 52x-555-3XXX
CIPT1 v8.09

10.x.1.0/24

CUCM2-x

Translate called number of incoming PSTN calls from 52x555-3XXX to 2XXX


.1

CUCM1-x

Add prefixes to the calling number of incoming PSTN calls

2010 Cisco Systems, Inc. All rights reserved.

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC Cisco IP Phones


Lab Guide 39

2010 Cisco Systems, Inc.

Cisco IOS MGCP gateway PSTN with PSTN phone

Job Aids
This job aid is available to help you complete the lab activity. Transformation Masks (Where x Is Your Pod Number)
Cluster Name Pod x IP Phones Phone1-x, Phone2-x, Phone3-x External Phone Number Mask 52x5553XXX

Note

Be aware that the DID number range is different to the internally assigned directory numbers. For example, to reach Phone1-1 (2001) from the PSTN, the DID number would be 5215553001.

Task 1: Configure Cisco Unified Communications Manager to Strip Access Codes That Are Used for Called Numbers on Outgoing Calls
In this task, you will configure access-code stripping for the MGCP gateway by using calledparty transformations that will be applied at the gateway.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10

Go to Call Routing > Class of Control > Partition, and click Add New. Enter MGCP_called_trans as the partition name, and click Save. Go to Call Routing > Class of Control > Calling Search Space, and click Add New. Enter MGCP_called_trans as the CSS name, and move the MGCP_called_trans partition to the Selected Partitions field. Click Save. Go to Call Routing > Transformation > Transformation Pattern > Called Party Transformation Pattern, and click Add New. Define the pattern 9.! and choose MGCP_called_trans from the Partition dropdown list. In the Discard Digit Instructions drop-down list, choose PreDot and click Save. Click Add New and then repeat Step 7 and Step 8 for defining Transformation Pattern 9.!#. Click Add New and then repeat Step 7 and Step 8 defining Transformation Pattern 911 without any digit manipulation.
The 911 Transformation Pattern is required to avoid matching the 9.! Transformation Pattern where the leading 9 is stripped off.

Note

Step 11
40

Go to Device > Gateway and click Find.


2010 Cisco Systems, Inc.

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Step 12 Step 13 Step 14 Step 15 Step 16 Note

At the listed MGCP Gateway (HQ-x), open the See Endpoints link and open the displayed endpoint. Scroll down to the Call Routing InformationOutbound Calls field and uncheck Use Device Pool Called Party Transformation CSS. At the Called Party Transformation CSS drop-down menu, choose MGCP_called_trans and click Save and Reset. Access the HQ-x router via telnet and reset the MGCP process using the no mgcp command followed by the mgcp command from global configuration mode. At gateway HQ-x, enter the debug isdn q931 command in enable mode.
As you access HQ-x via Telnet, do not forget to use the terminal monitor command to see the debug output.

Step 17

From one of your IP phones, dial a PSTN number and verify that the dialed PSTN access code 9 is not sent to the PSTN.

Activity Verification
You have completed this task when you attain this result:

At gateway HQ-x, you see that the access code was removed from the called number.

Task 2: Configure Cisco Unified Communications Manager to Extend Calling Numbers in Outgoing Calls to Fully Qualified PSTN Numbers
In this task, you will configure external phone number masks or transformation masks to extend directory numbers to fully qualified PSTN numbers.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Note

Go to Device > Phone and click Find. Choose Phone1-x. At the Phone Configuration page, click Line [1] to get to the Line Configuration page of the phone. Enter an External Phone Number Mask of 52x5553XXX. Click Save. Repeat this procedure for Phone2-x, Phone3-x, and Phone4-x. Reset all four phones from the Find and List Phones page.
Make sure that you also reset the third-party SIP phone itself. At the PC, close and restart the x-lite SIP softphone application.

Step 8 Step 9 Step 10

Go to Call Routing > Route/Hunt> Route Pattern and click Find. Enter the Route Pattern Configuration window by clicking the route pattern 9.!. In the Calling Party Transformations pane, check the Use Calling Party's External Phone Number Mask check box.
Lab Guide 41

2010 Cisco Systems, Inc.

Step 11 Step 12 Step 13

Click Save. Repeat this procedure for route pattern 9.!#. Place a call to the PSTN phone from one of your IP phones. Before accepting the call at the PSTN phone, verify that the calling number is shown as a 10-digit PSTN number rather than a 4-digit extension.

Activity Verification
You have completed this task when you attain this result:

On outgoing PSTN calls, the calling number is shown as 10-digit PSTN number (52x5553XXX). This number can be verified at the PSTN phone that receives the call or by examining the debug isdn q931 command output at the gateway (HQ-x).

Task 3: Configure Cisco Unified Communications Manager to Reduce the Called PSTN Number of Incoming Calls to Directory Numbers
In this task, you will configure translation patterns for the called number of incoming PSTN calls to change the dialed called PSTN numbers to internally used directory numbers.

Activity Procedure
Complete these steps: Try to Place Calls from the PSTN into Your Cluster Step 1 Try placing a call from the PSTN phone to Phone1-x (2001) by dialing 1-52x-5553001. The call will fail. When looking at debug isdn q931 output at HQ-x, you will realize that the PSTN tries to set up the call to 52x5553001. Cisco Unified Communications Manager rejects the call because no phone is configured with such a long number; internally, four-digit directory numbers are used. Also, the internally assigned directory number range 2XXX does not match the extensions used by DID calls (3XXX). Enable Calls from the PSTN into Your Cluster Step 2 To allow incoming calls from the PSTN, go to Call Routing > Translation Pattern and click Add New. This translation pattern should translate called numbers for calls coming from the PSTN from 10-digit PSTN numbers to the 4-digit directory number.
Step 3 Step 4 Step 5 Step 6 Step 7 Step 8

In the Translation Pattern field, enter 52x5553XXX (where x is your pod number). In the Description field, enter Translation of incoming 10-digit PSTN calls. Make sure that the Provide Outside Dial Tone box is unchecked. In the Called Party Transform Mask field, enter 2XXX. Click Save. Click Copy to create a copy of the translation pattern. This translation pattern should translate called numbers for calls coming from the PSTN from seven-digit PSTN numbers to the four-digit directory number. Change the Translation Pattern field to 5553XXX. In the Description field, enter Translation of incoming 7-digit PSTN calls. Click Save.
2010 Cisco Systems, Inc.

Step 9 Step 10 Step 11


42

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Note

When internal directory numbers match the DID extensions, setting the significant digits at the HQ-x gateway to 4 would be easier. This setting will trim the called number on incoming calls to the last four digits.

Route Calls Placed to Unassigned Directory Numbers to an Attendant Step 12 At the Translation Pattern Configuration page, click Add New to create another translation pattern.
Step 13 Step 14 Step 15 Step 16 Step 17

In the Translation Pattern field, enter 2XXX. In the Description field, enter Translation for Unassigned Directory Numbers. Make sure that the Provide Outside Dial Tone box is unchecked. In the Called Party Transform Mask field, enter 2002. Click Save.

Activity Verification
You have completed this task when you attain this result:

You can place calls from the PSTN phone to the IP phones in your pod. Dial 1-52x-555-3001. Phone1-x rings. Dial 555-3002. Phone2-x rings. Dial 1-52x-555-3004. Phone4-x rings. Dial 555-3009. Phone2-x rings because 2009 is an unassigned directory number and therefore, after performing the first translation from 5553009 to 2009, the called number matches translation pattern 2XXX, which translates the called number to 2002.
Depending on the line that you use at the PSTN phone, calls are received from different calling numbers. However, all calling numbers use the PSTN format, so they do not include access code 9 (or 1 for long-distance numbers), which are required for callback from call lists. The displayed number in call lists must be edited to be able to call back a number.

Note

Task 4: Configure Cisco Unified Communications Manager to Prefix Access Codes to Calling Numbers on Incoming PSTN Calls
In this task, you will configure Incoming Calling Party Settings on the MGCP gateway, so that received or missed PSTN calls can be called back from call lists without the need to edit the number.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3

Go to Device > Gateway and click See Endpoints at the HQ-x MGCP gateway. Select the shown device name and scroll down to the Incoming Calling Party Settings pane. For the National Number Type enter 91 at the Prefix field, for the Subscriber Number Type enter 9 at the Prefix field, and for the International Number Type enter 9011 at the Prefix field.
Lab Guide 43

2010 Cisco Systems, Inc.

Step 4 Step 5

Click Save and Reset the Gateway. Also reset the MGCP process at the HQ-x router by issuing the no mgcp followed by the mgcp command in global configuration mode.

Activity Verification
You have completed this task when you attain this result:

You can place a call from the PSTN phone to one of the IP phones in your pod. From line 2 (national) of the PSTN phone, dial the long-distance number of Phone1x (1-52x-555-3001). You see that the call is received from 916065554444. From line 1 (local) of the PSTN phone, dial the local number of Phone2-x (5553002). You see that the call is received from 95554444.

Task 5 (Optional): Implement E.164 Plus Dialing and Phone Number Localization
In this task, you will add an E.164 phone number with a + prefix to your personal directory and then localize the number when sending the call to the PSTN.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3 Step 4 Step 5

Go to User Management > End User and click Find. Select User3. At the Device Information pane click the Device Association, button, then check the checkbox for Phone3-x and click Save Selected/Changes. Open the user web pages (https://10.x.1.1/ccmuser) and log on User3. Add the following entry to the Personal Address Book of User3:

Mobile Phone: +776065554444. First Name: Andreas Last Name: Szoldatics Nick Name: Andy

Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13

Log off User3 and log on to Cisco Unified Communications Manager Administration web pages again. Navigate to Call Routing > Translation Pattern and click Add New. In the Translation Pattern field, enter \+.! In the Description field, enter Translation for E.164 calls. Make sure that the Provide Outside Dial Tone box is unchecked. From the Discard Digit Instruction drop-down menu, choose PreDot. Enter 9011 in the Called Party Prefix field. Click Save.

44

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Activity Verification
You have completed this task when you attain these results:

The call rings on the international line on the PSTN phone. On Phone3-x, press the Directories button and open the personal directory. Login User3 and select Personal Address Book. Press the Submit softkey to display the previously created contact entry and dial the number that is associated with it. Observe the localization of the called E.164 number while the call rings at the international PSTN line.

Step 1 Step 2 Step 3 Step 4

2010 Cisco Systems, Inc.

Lab Guide

45

Lab 4-4: Implementing Calling Privileges in Cisco Unified Communications Manager


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will implement calling privileges in Cisco Unified Communications Manager. After completing this activity, you will be able to meet these objectives:

Configure partitions and CSSs Implement CoS for internal calls Implement CoS for outgoing PSTN calls Implement CoS for incoming PSTN calls Implement time-of-day-based CoS Implement FAC

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 4-4: Implementing Calling Privileges in Cisco Unified Communications Manager


Phone1-x Phone2-x Phone3-x

PSTN
DHCP DHCP DHCP

10.x.2.0/24 PC-x HQ-x


DHCP .2 .101

PSTN

10.x.3.0/24

.101 .101

10.x.1.0/24

CUCM2-x

Implement CoS for internal calls


.1

Implement time-ofday based CoS Implement FAC

Implement CoS for incoming and outgoing PSTN calls

CUCM1-x

2010 Cisco Systems, Inc. All rights reserved.

CIPT1 v8.010

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC with X-Lite third-party freeware SIP softphone Cisco IP Phones

46

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Cisco IOS MGCP gateway PSTN with PSTN phone

Job Aids
These job aids are available to help you complete the lab activity. Partitions
Partition Name Lobby-Phones Phones Description Lobby phones Employee phones and 2XXX Assigned to Devices 2001 2002 2004 Translation patterns: 2XXX, 52x5553XXX, 5553XXX 2003 Assigned to Route Patterns 9.[2-9]XXXXXX 9.1[2-9]XX[2-9]XXXXXX 9.011! 9.011!# 9.011! 9.011!# 911 9.911 9.1[800]XXXXXXX

Manager-Phones Partition Name PSTN-Local_LD PSTN-Intl_ToD PSTN-Intl_FAC PSTN-Emergency PSTN-Free

Manager phones Description PSTN: Local and long distance PSTN: International, office hours only PSTN: International, FAC PSTN: Emergency PSTN: Toll free

Calling Search Spaces


Devices Lobby IP phone (2001) Employee IP phone (2002, 2004) CSS Name Lobby_css Description CSS for lobby phones Contains Partitions Phones PSTN-Emergency Phones_css CSS for employee phones Lobby-Phones Phones Manager-Phones PSTN-Emergency PSTN-Free PSTN-Local_LD PSTN-Intl_ToD Manager IP phone (2003) Manager_css CSS for manager phones Lobby-Phones Phones Manager-Phones PSTN-Emergency PSTN-Free PSTN-Local_LD PSTN-Intl_ToD PSTN-Intl_FAC

2010 Cisco Systems, Inc.

Lab Guide

47

Devices PSTN gateway(s) Translation patterns: 2XXX, 52x5553XXX, 5553XXX

CSS Name To-Phones_css

Description CSS for gateways and translation patterns

Contains Partitions Phones

Route Patterns
Route Pattern 911 9.911 9.1800XXXXXXX 9.[2-9]XXXXXX 9.1[2-9]XX[2-9]XXXXXX 9.011! 9.011!# 9.011! 9.011!# Route Partition PSTN-Emergency PSTN-Emergency PSTN-Free PSTN-Local_LD PSTN-Local_LD PSTN-Intl_ToD PSTN-Intl_ToD PSTN-Intl_FAC PSTN-Intl_FAC Description PSTN: Emergency PSTN: Emergency PSTN: Toll free PSTN: Local PSTN: Long distance PSTN: International, office hours only PSTN: International, office hours only PSTN: International, FAC outside office hours PSTN: International, FAC outside office hours Gateway/Route List RL_HQ_GWs RL_HQ_GWs RL_HQ_GWs RL_HQ_GWs RL_HQ_GWs RL_HQ_GWs RL_HQ_GWs RL_HQ_GWs RL_HQ_GWs

Task 1: Configure Partitions and CSSs


In this task, you will create partitions and CSSs in Cisco Unified Communications Manager Administration.

Activity Procedure
Complete these steps: Configure Partitions
Step 1 Step 2

Go to Call Routing > Class of Control > Partition, and click Add New. Using the partition configuration data from the Partitions table (in the Job Aids section of this lab exercise), enter all partition names and their descriptions, using this format: <partitionName> , <description> <partitionName> , <description> ...

Step 3

Click Save. Go to Call Routing > Class of Control > Calling Search Space, and click Add New to open the Calling Search Space Configuration window. Using the Calling Search Spaces table (in the Job Aids section of this lab activity), enter the first CSS name and description.
2010 Cisco Systems, Inc.

Configure CSSs
Step 4 Step 5

48

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Step 6

Using the information in the Calling Search Spaces table column Contains Partitions, highlight the appropriate partitions in the Available Partitions pane and add them to the Selected Partitions by using the Down arrow. To remove a partition from the list of Selected Partitions, highlight the partition and click the Up arrow.
Use the Shift key to highlight multiple contiguous entries and the Ctrl key to choose multiple noncontiguous entries.

Note

Step 7 Step 8

Click Save. Repeat the previous steps to create the remaining CSSs that are listed in the Calling Search Spaces table.
When you configure the Manager_css CSS, make sure that the PSTN-Intl_ToD partition is set before the PSTN-Intl_FAC partition. This order is important when time-of-day routing is implemented and a FAC must be entered if international calls are placed outside business hours.

Note

Activity Verification
You have completed this task when you attain these results:

When you navigate to Call Routing > Class of Control > Partition and click Find, you see all the partitions that you added. When you navigate to Call Routing > Class of Control > Calling Search Space and click Find, you see all the CSSs that you added.
Further verification will be performed during the following tasks.

Note

Task 2: Implement CoS for Internal Calls


In this task, you will configure Cisco Unified Communications Manager to provide CoS to internal destinations.

Activity Procedure
Complete these steps: Assign Partitions and CSSs to IP Phones Step 1 Go to Device > Phone and click Find.
Step 2 Step 3 Step 4 Step 5 Step 6

Click the IP phone with the directory number 2001, to open the Phone Configuration page. Click Line [1]2001 from the left page column, to access the Directory Number Configuration page. Choose Lobby-Phones for the Route Partition, and in the Directory Number Settings, choose Lobby_css for the Calling Search Space parameter. Click Save. Repeat Steps 1 through 5 for the other three IP phones in your cluster. Refer to the tables Partitions and Calling Search Spaces in the Job Aids section to locate the partition and the CSS configuration parameters that are applicable to these remaining IP phones.

2010 Cisco Systems, Inc.

Lab Guide

49

Step 7

Go to Device > Phone and click Find, then choose all four IP phones and click Reset Selected. Click Reset again, and click Close in the pop-up window.

Activity Verification
You have completed this task when you attain these results:

The lobby IP phone (2001) is able to call only employee IP phones (2002 and 2004) and cannot dial the manager IP phone (2003).
At this time, the translation pattern 2XXX will match for a call from 2001 to 2003.

Note

The employee IP phones (2002 and 2004) are able to call all other IP phones. The manager IP phone (2003) is able to call all other IP phones.

Task 3: Implement CoS for Incoming PSTN Calls


In this task, you will configure Cisco Unified Communications Manager to provide CoS for incoming PSTN calls. PSTN callers should not be able to call lobby and manager phones. If they try, the call should be sent to the attendant (2002).

Activity Procedure
Complete these steps: Assign Partitions and CSSs to Translation Patterns Step 1 Go to Call Routing > Translation Pattern and click Find.
Step 2 Step 3 Step 4 Step 5 Step 6

Click the translation pattern 2XXX to open the Translation Pattern Configuration window. Choose Phones from the Partition drop-down menu. Choose To-Phones_css from the Calling Search Space drop-down menu. Click Save. Repeat the previous steps for the 52x5552XXX and the 5553XXX translation patterns.

Assign Partitions and CSSs to Gateways Step 7 Choose Device > Gateway, and click Find to list all the gateways.
Step 8 Note

At the HQ-x MGCP gateway, click the See Endpoints link in the Status column.
Each endpoint of an MGCP gateway is controlled separately; therefore CSSs are applied individually per endpoint and not at the gateway level.

Step 9 Step 10

Choose the Device Name (for example, S0/SU0/DS1-0@HQ-x) to access the Endpoint Configuration page. Scroll down the page to see the Call Routing InformationInbound Calls section, in which the CSS can be configured. Set the appropriate CSS according, to the job aid table. Click Save and reset the MGCP endpoint.

Step 11

50

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Note

You also have to reset the mgcp process directly at the HQ-x gateway by issuing no mgcp command followed by mgcp command in global configuration mode.

Activity Verification
You have completed this task when you attain these results:

The PSTN phone is able to call employee phones (555-3002 or 555-3004). If the PSTN dials the manager or lobby IP phone (555-3001 or 555-3003), the call is sent to the attendant (2002). If an unassigned directory number is dialed from the PSTN phone (for example, 555-3010), the call is sent to the attendant (2002).

Task 4: Implement CoS for Outgoing PSTN Calls


In this task, you will configure Cisco Unified Communications Manager to provide CoS for outgoing PSTN calls to emergency, local, long-distance, and toll-free PSTN destinations. You will also configure route patterns to international destinations, which will be restricted in the next task.

Activity Procedure
Complete these steps: Create and Update Route Patterns for CoS in Cisco Unified Communications Manager In this step, you will create different route patterns for different call types (emergency, toll-free, local, long-distance, and international). The existing route patterns (9.!# and 9.!) will be changed to emergency route patterns; all other route patterns will be added.
Step 1 Step 2 Step 3 Step 4 Step 5 Note Step 6 Step 7

Go to Call Routing > Route/Hunt > Route Pattern and click Find. Choose the 9.! route pattern. Change the route pattern to 911 and the description to PSTN Emergency. Set the partition to PSTN-Emergency. Check the Urgent Priority check box.
The DDI will be unavailable because it is no longer applicable.

Save your changes. Repeat the previous steps but change the 9.!# route pattern to 9.911. Set the partition to PSTN-Emergency, change the description to PSTN Emergency, and check the Urgent Priority check box. Do not forget to save your changes. Click the Copy button in the Route Pattern Configuration window and update the following parameters with the values of the next route pattern that is shown in the Route Patterns table of the Job Aids section.

Step 8

Route Pattern: 9.1800XXXXXXX Route Partition: PSTN-Free Description: PSTN: Toll Free Urgent Priority: Uncheck

2010 Cisco Systems, Inc.

Lab Guide

51

Note

You do not need to configure PreDot digit stripping at the route pattern because this is performed directly at the gateway, using the called-party transformation CSS.

Step 9 Step 10

Click Save. And on the subsequent pop-up windows, click OK. Repeat the last two steps to create the remaining route patterns as described in the Route Patterns table in the Job Aids section.
If you decide to add the new route patterns from scratch instead of copying them from the existing route pattern, make sure that you click the Use Calling Party's External Phone Number Mask check box at all route patterns that you add.

Note

Activity Verification
You have completed this task when you attain these results:

When you go to Call Routing > Route/Hunt > Route Pattern and click Find, you see the newly created route patterns in the appropriate partitions. The lobby IP phone (Phone1-x) can dial only one PSTN destination: emergency numbers (9-911 or 911). The employee IP phones (Phone2-x and Phone4-x) and the manager IP phone (Phone3-x) are able to call all supported PSTN destinations (for example, local: 9-555-4444, long distance: 9-1-666-555-4444, international: 9-011-43-555 4444, emergency: 9-911 or 911, and toll free: 9-1-800-555-4444).
At this stage, ignore the route pattern in partition PSTN-Intl_FAC. That pattern is irrelevant here because it is identical to the route pattern PSTN-Intl_ToD. Also, note that partition PSTN-Intl_ToD does not have a time schedule that is applied at this point and therefore is always active in the CSSs that include this partition.

Note

Task 5 (Optional): Implement Time-of-Day-Based CoS


In this task, you will configure Cisco Unified Communications Manager to allow international calls from employee phones only during business hours. Manager phones will still have unlimited access to international calls. This configuration will be done by applying a time schedule to the PSTN-Intl_ToD partition. The corresponding partitions and route patterns have already been configured in previous tasks.

Activity Procedure
Complete these steps: Create a Time Period Step 1 Go to Call Routing > Class of Control > Time Period and click the Add New button.
Step 2

In the Time Period Configuration window, enter the following parameters:


Name: 9a-5p_Mo-Fr Time Of Day Start: 00:00 Time Of Day End: 24:00 Repeat Every Week from Monday to Sunday

Step 3
52

Click Save.
2010 Cisco Systems, Inc.

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Note

The requirement in this task is to permit calls during business hours, such as 9:00 a.m. (0900) to 5:00 p.m. (1700), as indicated in the name of the time period. However, to easily simulate a call that is placed within business hours and a call that is placed outside business hours, the period is first set to 24 hours, repeated from Monday to Sunday. This will ensure that the call will match the configured time range and allows the simulation of calls that are placed within business hours. Then, the time period will be changed to a very small time slot, which will not match the current day and time. This allows the simulation of calls that are placed outside business hours. In reality, you would configure something like 9:00 a.m. (0900) to 5 p.m. (1700) hours, Monday to Friday, to achieve the requirement of limiting international calls to business hours.

Create a Time Schedule Step 4 Go to Call Routing > Class of Control > Time Schedule and click Add New.
Step 5 Step 6 Step 7

In the Time Schedule Configuration window, enter BusinessHours in the Name field, and click Save. Move the 9a-5p_Mo-Fr time period from the Available Time Periods pane in the Selected Time Periods. Click Save.

Assign the Time Schedule to the ToD Partition Step 8 Navigate to Call Routing > Class of Control > Partition and click Find.
Step 9 Step 10 Step 11

Click the partition with the name PSTN-Intl_ToD. In the Partition Configuration window, choose the newly created time schedule BusinessHours in the Time Schedule field. Click Save.

Activity Verification
You have completed this task when you attain these results:

You have created a time schedule and time period. Employee phones can dial international destinations during business hours only. To verify your configuration, follow these steps: From Phone2-x or Phone4-x, dial any international number (for example, 9-011-43555 4444). At the moment, the time period is configured to cover the whole week (00002400 hours, Monday to Friday). Because the call is placed within the specified time, it is considered to be within business hours and therefore is permitted. To simulate a call outside business hours, go to Call Routing > Class of Control > Time Period and click Find. Choose the 9a-5p_Mo-Fr time period and change the time range to values that do not include the current time as displayed at your IP phones (for example, 00:0000:15, Monday to Monday), and click Save. Try placing an international call again from Phone2-x or Phone4-x. Because the call is not placed within the specified time, it is considered to be outside business hours and is denied.

Step 1

Step 2

Step 3

2010 Cisco Systems, Inc.

Lab Guide

53

Note

At this stage, manager phones have access to international route patterns in partition PSTNIntl_ToD, which is now limited to business hours and in partition PSTN-Intl_FAC, which is not limited at all at this point. If partition PSTN-Intl_ToD is removed from the manager phone CSS, the route pattern is still visible from the PSTN-Intl_ToD partition. Therefore, manager phones can still call international destinations at any time.

Task 6 (Optional): Implement FACs


In this task, you will configure Cisco Unified Communications Manager to require a FAC to be entered at manager phones when dialing international destinations outside business hours.

Activity Procedure
Complete these steps: Configure Forced Authorization Code Step 1 Go to Call Routing > Forced Authorization Codes and click Add New.
Step 2

In the Forced Authorization Code Configuration window, enter the following parameters:

Authorization Code Name: International Calls Outside Business Hours Authorization Code: 9999 Authorization Level: 5

Step 3 Step 4 Step 5

Click Save. Repeat the previous steps to add another FAC with name Too Low Level, code 9998, and level 4. Go to Call Routing > Route/Hunt > Route Pattern and click Find. From the displayed list, click the 9.011! route pattern, which is in the PSTN-Intl_FAC partition. In the Route Pattern Configuration window, check the Require Forced Authorization Code check box. Set the minimum required Authorization Level to 5. Click Save. Repeat the previous steps for the 9.011!# route pattern in the PSTN-Intl_FAC partition.

Step 6

Step 7 Step 8

Activity Verification
You have completed this task when you attain these results:

Outside business hours, manager phones should be able to dial international destinations only after entering a valid FAC with a high-enough authorization level. To verify your configuration, follow these steps: Dial an international destination (for example, 9-011-43-555 4444) from the manager IP phone. Assuming that your time period configuration is still set to a range that does not include the current day and time, a beep should be heard and Enter Authorization Code is displayed on the IP phone, indicating that an FAC needs to be entered. Enter FAC 9999 followed by # and the call should be permitted.

Step 1

Step 2

54

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Step 3

Dial the same number again, but this time enter FAC 9998 followed by #. The call should be denied because the authorization level configured for FAC 9998 is not high enough for the matched route pattern. Dial the same number again, but this time enter an invalid FAC (for example, 9997) followed by #. The call should be denied. Change the time period back to 00:00 to 24:00, Monday to Friday (as described in the previous task). Dial the same number again. This time there will be no prompt for an FAC.
The CSS of the manager phone has partition PSTN-Intl_ToD listed before partition PSTNIntl_FAC. If the ToD partition is active (that is, during business hours) a route pattern that does not require an FAC is matched. If the call is placed outside business hours, the partition PSTN-Intl_ToD is not active in the phone CSS and therefore the route pattern that is in the PSTN-Intl_FAC partition is matched. This route pattern requires an FAC to be entered. If the partitions were configured in the wrong order (PSTN-Intl_FAC before PSTNIntl_ToD) in the CSS, the manager phone would always require an FAC to be entered, even during business hours.

Step 4 Step 5 Step 6 Note

2010 Cisco Systems, Inc.

Lab Guide

55

Lab 4-5: Implementing Call Coverage in Cisco Unified Communications Manager


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this task, you will configure hunt groups that consist of line groups, hunt lists, and a hunt pilot number with internal and external forwarding settings for busy, no-answer, and no-callcoverage conditions. After completing this activity, you will be able to meet these objectives:

Configure call hunting, including line groups, hunt lists, and hunt pilots Configure final forwarding on hunt exhaustion

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 4-5: Implementing Call Coverage in Cisco Unified Communications Manager


Phone1-x Phone2-x Phone3-x

2nd Line Group

PSTN

DHCP

DHCP

DHCP

10.x.2.0/24 PC-x

PSTN

1st Line Group


DHCP .2

HQ-x 10.x.3.0/24
.101 .101

.101

10.x.1.0/24

CUCM2-x

.1

Configure line groups, hunt list, hunt pilot, and final forwarding

CUCM1-x

2010 Cisco Systems, Inc. All rights reserved.

CIPT1 v8.011

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC with X-Lite third-party freeware SIP softphone Cisco IP Phones Cisco IOS MGCP gateway PSTN with PSTN phone

56

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Task 1: Create a Line Group and Add Members


In this task, you will create two line groups and add members to the new line groups. You will create a 1stLG line group and add directory numbers 2001 and 2003 to it and a 2ndLG line group with directory number 2002 assigned to it.

Activity Procedure
Complete these steps: Create a Line Group
Step 1 Step 2 Step 3

Choose Call Routing > Route/Hunt > Line Group and click Add New. Enter 1stLG in the Line Group Name field. For now, leave the distribution algorithm at the default (Longest Idle Time). Leave the hunt options for Busy, No Answer, and Not Available at their default values (Try Next Member; Then, Try Next Group in Hunt List). Change the Ring NoAnswer Reversion (RNAR) Timeout from its default value of 10 seconds to 5 seconds.
This value might not be appropriate in a call center environment, however, in a classroom or test environment, a shorter timeout enables you to validate call-distribution behavior more quickly.

Step 4

Note

Add Members to the Line Group You will add the 2001 and 2003 directory numbers to the line group.
Step 5

In the Available DN/Route Partition pane, choose 2001/Lobby-Phones and click Add to Line Group to move it to the Selected DN/Route Partition pane. Repeat this step to add 2003/Manager-Phones to this line group. The order of the directory numbers in the Selected DN/Route Partition pane determines the order in which the directory numbers are accessed in this line group. Change the order of the line group members so that 2003 is the first member and 2001 is the second member. To change the order, click a directory number and use the Up and Down arrows or choose Reverse Order of Selected DNs. Click Save to add the new directory numbers to the line group. Repeat the previous steps to create a second line group named 2ndLG with member 2002/Phones.

Step 6

Step 7 Step 8

Activity Verification
You have completed this task when you attain this result:

Two line groups with their respective members have been added to Cisco Unified Communications Manager. You can see these two line groups if you choose Call Routing > Route/Hunt > Line Group and click Find.

2010 Cisco Systems, Inc.

Lab Guide

57

Task 2: Create a Hunt List and Add Line Groups


In this task, you will create a hunt list called 1stHL and add the 1stLG and 2ndLG line groups to it.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

Go to Call Routing > Route/Hunt > Hunt List. Click Add New. In the Hunt List Name field, enter the name 1stHL. In the Description field, enter First Hunt List. From Cisco Unified Communications Manager Group drop-down list, choose Default. Check the Enable this Hunt List check box and click Save. Add the previously created line groups to the new hunt list. Click Add Line Group. The Hunt List Detail Configuration window appears. From the Line Group drop-down list, choose the 1stLG line group, and then click Save. Click OK on the pop-up window. The line group name will appear in the Hunt List Configuration window in the Selected Groups pane. Click the Add Line Group button again, and repeat the previous step to add the remaining line group, 2ndLG, to the hunt list.
Cisco Unified Communications Manager accesses line groups in the order in which they appear in the hunt list. You can change the access order of line groups, if necessary, by choosing a line group from the Selected Groups list and clicking the Up or Down arrow on the right side of the pane to move the line group up or down in the list.

Step 8

Note

Step 9 Step 10

Click Save in the Hunt List Configuration window. Then click OK on the pop-up that reminds you to reset the hunt list. Click Reset to reset the hunt list. When the dialog window appears, click Reset, and then click Close.

Activity Verification
You have completed this task when you attain this result:

One hunt list that contains two line groups has been added to Cisco Unified Communications Manager. You can verify that by choosing Call Routing > Route/Hunt > Hunt List and then clicking Find.

Task 3: Create a Hunt Pilot Number and Associate It with a Hunt List
In this task, you will create a hunt pilot number, 2111, and assign it to the 1stHL hunt list.

Activity Procedure
Complete these steps:
Step 1 Step 2
58

Choose Call Routing > Route/Hunt > Hunt Pilot. Click Add New.
2010 Cisco Systems, Inc.

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Step 3 Step 4 Step 5 Step 6

Enter 2111 in the Hunt Pilot Number field and Hunt Pilot 1 in the Description field. Choose partition Phones from the Route Partition drop-down list. Assign the hunt pilot to the 1stHL hunt list using the Hunt List field drop-down menu. Click Save.

Activity Verification
You have completed this task when you attain this result:

You created a hunt pilot number 2111 and assigned it to the hunt list: Go to Call Routing > Route/Hunt > Hunt Pilot and click Find to verify that your hunt pilot has been created correctly.

Task 4: Test Call Distribution


In this task, you will test and validate the call-distribution behavior to ensure that it operates as desired.

Activity Procedure
Complete these steps:
Step 1

From the IP phone with the directory number 2004 (Phone4-x), call the hunt pilot number 2111 and observe the call distribution behavior. Answer the call when it rings on 2003.
Directory number 2001 should now be the member with the longest idle time in the first line group (1stLG) and therefore should ring first when the next call is placed to the hunt pilot number.

Note

Step 2

Call 2111 again and verify that the call is first sent to 2001. Do not answer the call. After 5 seconds (RNAR timeout), the call should be sent to 2003. Again, do not answer the call. After another 5 seconds the call is sent to 2002, a member of the second line group (2ndLG). The call is passed on to a member of the second line group because Try Next Member, Then, Try Next Group in Hunt List is specified as the hunt option. The number 2002 will ring for 5 seconds, then hunting fails. To be able to run into a busy condition on a phone line, you need to set the busy trigger to 1 (at the Line Configuration page). This configuration disables call waiting, allowing a directory number to receive only one call at a time and generate a busy signal for additional callers. Perform the following steps to enable a busy condition on line 2001:

Step 3

Go to Device > Phone, click Find, and click Phone1-x. At the Phone Configuration page, click line 1 to get to the Line Configuration page. At the Line Configuration page, scroll down to the Multiple Call/Call Waiting settings. Change the value of the Busy Trigger parameter to 1. Click Save and then reset the line.

Step 4

Repeat the previous step for Phone3-x.

2010 Cisco Systems, Inc.

Lab Guide

59

Step 5

Place a call from 2003 to 2001 and keep the call open to generate a busy condition. What do you expect will happen when you call the hunt pilot from 2004? Write down your assumption and then test your hypothesis. Hang up the call between 2001 and 2003. Spend a few moments experimenting with other line group distribution algorithms (Circular, Broadcast, or Top-Down) and other hunt options (Stop Hunting; Skip Remaining Members, and Go Directly to Next Group; and Try Next Member, but Do Not Go to the Next Group).

Step 6

Activity Verification
You have completed this task when you attain this result:

Calls to the hunt pilot will hunt and achieve call distribution according to the configured hunt option and distribution algorithm.
More specific verification was part of the activity procedure.

Note

Task 5 (Optional): Configure Final Forwarding for Busy and NoAnswer Conditions
In this task, you will configure final forwarding on the hunt pilot number so that a call that is forwarded to the hunt pilot and that is not answered (because of no-answer or busy conditions) is forwarded to a local PSTN number. In a production network, the final forwarding destination is usually set to the number of an auto-attendant or voice-mail system.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3

Choose Call Routing > Route/Hunt > Hunt Pilot, and then click Find. Choose 2111 to go to the Hunt Pilot Configuration window. In the Hunt Forward Settings section, configure these final forwarding settings:

Forward Hunt No Answer Destination: 2001 Forward Hunt No Answer CSS: Phones_css Forward Hunt Busy Destination: 95554444 Forward Hunt Busy CSS: Phones_css Maximum Hunt Timer: 12 seconds

Step 4 Step 5 Step 6 Step 7

Click Save. Choose Call Routing > Route/Hunt > Line Group, and click Find. Choose 1stLG to go to the Line Group Configuration window. Set the call-distribution algorithm to Top Down, the hunt option for No Answer and Not Available to Try Next Member, Then, Try Next Group in Hunt List, and the hunt option for Busy to Try Next Member, But Do Not Go to Next Group. Click Save. From Phone4-x (2004), call the hunt pilot number 2111 and do not answer the call. What do you expect will be the call-distribution and final forwarding behavior?

Step 8 Step 9

60

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Write down your assumption and then test your hypothesis. ________________________________________________________________
Step 10

Place a call from 2003 to 2001 and keep the call open, to generate a busy condition. From Phone4-x, call the hunt pilot number 2111. What do you expect will be the call-distribution and final forwarding behavior? Write down your assumption and then test your hypothesis. ________________________________________________________________ Hang up all calls.

Step 11

Activity Verification
You have completed this task when you attain these results:

When not answering the call, final forwarding to directory number 2001 is performed after 12 seconds of hunting. At Phone1-x, Forwarded for 2111 appears on the display. When Phone1 and Phone3 are busy, the call will not be sent to the next group (2002) but will be forwarded to the local line of the PSTN phone.

Cleanup
To prepare for future labs, follow the procedure that was described in the previous task to change the Busy Trigger parameter at line 2001. This time set the parameter back to 2.

2010 Cisco Systems, Inc.

Lab Guide

61

Lab 5-1: Implementing Media Resources


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure media resources in Cisco Unified Communications Manager and control access to these media resources. After completing this activity, you will be able to meet these objectives:

Add a software conference media resource in Cisco Unified Communications Manager Configure a hardware conference media resource in Cisco IOS router and add it to Cisco Unified Communications Manager Configure Meet-Me conferences in Cisco Unified Communications Manager Manage MOH audio files Configure multicast MOH Implement media resources access control

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 5-1: Implementing Media Resources


Phone1-x Phone2-x Phone3-x

Use MOH and conferences

PSTN

DHCP

DHCP

DHCP

10.x.2.0/24 PC-x HQ-x


DHCP .2 .101

PSTN

10.x.3.0/24

.101 .101

10.x.1.0/24

CUCM2-x

.1

CUCM1-x

Configure media resources: MOH Hardware conference bridge Software conference bridge Implement media resource access control

Configure hardware conference bridge

2010 Cisco Systems, Inc. All rights reserved.

CIPT1 v8.012

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC with MOH audio file Cisco IP Phones
2010 Cisco Systems, Inc.

62

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Cisco IOS MGCP gateway PSTN with PSTN phone

Command List
The table describes the commands that are used in this activity. DSP Farm Cisco IOS Commands
Command Description Enters voice-card configuration mode to configure its resources Configures DSP farm services for a voice card Enables SCCP and its related applications (transcoding and conferencing) Selects the local interface that the SCCP applications should use to register with Cisco Unified Communications Manager Adds the Cisco Unified Communications Manager server to the list of available servers and sets its priority Specifies the maximum number of transcoding sessions to be supported by a DSP farm Specifies the maximum number of concurrent conference sessions for which DSP farm resources should be allocated Enables DSP farm services

voice-card card_number dsp services dspfarm sccp sccp local interface

sccp ccm CCM_ipaddress priority dspfarm transcoder maximum sessions dspfarm confbridge maximum sessions dspfarm

Task 1: Add a Software Conference Media Resource in Cisco Unified Communications Manager
In this task, you will add a software conference media resource in Cisco Unified Communications Manager and activate the Cisco IP Voice Media Streaming Application service.

Activity Procedure
Complete these steps: Activate the Cisco IP Voice Media Streaming Application Service Step 1 In the Cisco Unified Serviceability window, go to Tools > Service Activation.
Step 2 Step 3 Note

Choose the first node (10.x.1.1) from the Server drop-down menu. Activate the Cisco IP Voice Media Streaming App service.
The Cisco IP Voice Media Streaming App service can be activated on multiple servers.

Configure the Software Conferencing Media Resource Step 4 In the Cisco Unified Communications Manager Administration, go to Media Resources > Conference Bridge and click Find.
Step 5

You should see one software conference bridge per server. These servers are generated automatically during installation, with a description of CM_(server name as entered during installation). The name is usually CFB_2 for the first installed
Lab Guide 63

2010 Cisco Systems, Inc.

server, CFB_3 for the next installed server, and so on. The conference bridges are running only when the Cisco IP Voice Media Streaming App service is activated on the appropriate server.
Step 6 Step 7 Step 8 Step 9

Click the conference bridge name CFB_2 (the bridge of the publisher) to enter the Conference Bridge Configuration window. Change the name to SW-CFB_CUCM1-x. Change the Description to Software Conference Bridge CFB_CUCM1-x. Click Save.

Activity Verification
You have successfully completed this task when you attain these results:

In Tools > Service Activation, the Cisco IP Voice Media Streaming Application service is activated. In Media Resources > Conference Bridge, you can see the automatically generated conference bridge. When you go to Media Resources > Conference Bridge and click Find, you see that SWCFB_CUCM1-x is registered. Try to establish an ad-hoc conference with three participants. Specifically, perform these steps: Establish a call from Phone2-x to Phone1-x. At Phone2-x, press the More softkey to browse through the available softkeys. Press the Confrn softkey and dial 2003. At Phone3-x, accept the call. At Phone2-x, press the Confrn softkey. You should now have a conference with Phone1-x, Phone2-x, and Phone3-x as members. Use the ConfList softkey at Phone1-x and Phone2-x to show the Conference List. Note that the creator of the conference can also remove participants from the conference.

Step 1 Step 2 Step 3 Step 4 Step 5

Task 2: Add a Hardware Conference Media Resource


In this task, you will configure a hardware conference media resource on router HQ-x and add the hardware conference media resource to Cisco Unified Communications Manager.

Activity Procedure
Complete these steps: Configure a Cisco IOS Router as a Hardware Conference Media Resource Step 1 Connect to your HQ-x router and enter enable mode.
Step 2

Discover the current MAC address on the FastEthernet0/0 interface of your transcoder router and record it on the line that follows the example. Enter the show interface fastethernet0/0 command to see the output, which will be similar to this example. Make note of the MAC address that is shown in your output.

64

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

FastEthernet0/0 is up, line protocol is up Hardware is AmdFE, address is 000f.34d9.0d00 (bia 000f.34d9.0d00) (output truncated)

Write down the MAC address of your router:_______________________________


Note You must use the MAC address of the interface on which SCCP will be enabled in the name of the conference bridge, when using a Cisco IOS conference bridge. In this lab, the MAC address is not required because a Cisco IOS enhanced conference bridge is configured.

Step 3

Make router DSP resources available as a hardware conference bridge and have them registered at your Cisco Unified Communications Manager system. In global configuration mode, enter this sequence of commands:
voice-card 0 dspfarm dsp services dspfarm exit sccp local FastEthernet0/0.1x1 sccp ccm 10.x.1.1 identifier 1 version 7.0+ sccp ccm 10.x.1.2 identifier 2 version 7.0+

Note

When entering the sccp ccm command, use ? after the keyword version to find out which Cisco Unified Communications Manager versions are supported by this Cisco IOS version. Choose the one that is closest to your Cisco Unified Communications Manager version.

sccp sccp ccm group 1 associate ccm 1 priority 1 associate ccm 2 priority 2 associate profile 1 register HW-CFB_HQ-x exit
Note In this lab, a Cisco IOS enhanced conference bridge is configured. Therefore, the name of the conference bridge can be freely chosen. When configuring a Cisco IOS conference bridge, the name must be CFB<MAC >, where <MAC> is the MAC address of your SCCP interface (as determined in Step 2), without the dots. The name that is based on the output in Step 2 for example, would be CFB000F34D90D00.

dspfarm profile 1 conference codec g711ulaw codec g711alaw maximum sessions 2 associate application SCCP no shutdown exit

2010 Cisco Systems, Inc.

Lab Guide

65

Add the Cisco IOS Hardware Conference Media Resource to Cisco Unified Communications Manager Step 4 Connect to the publisher and, in Cisco Unified Communications Manager Administration, choose Media Resources > Conference Bridge to open the Find and List Conference Bridges page.
Step 5 Step 6 Step 7

Click Add New. From the Conference Bridge Type drop-down menu, choose Cisco IOS Enhanced Conference Bridge. For the conference bridge name, enter the name of your conference bridge as specified at the Cisco IOS router in the associate profile command (HW-CFB_HQx).
The name of the media resource is case-sensitive.

Tip Step 8 Step 9 Step 10 Step 11

For the Description, enter Hardware Conference Bridge CFB_HQ-x. Choose Default for the Device Pool. Choose Non Secure Conference Bridge for the Device Security Mode. Click Save.

Activity Verification
You have successfully completed this task when you attain these results:

Connect to your conference bridge router HQ-x and enter the show sccp command. Verify that the Conferencing Oper State is Active and that the TCP Link Status is Connected. Enter the show sccp ccm group 1 command. Verify that the group is associated with both Cisco Unified Communications Managers and the dspfarm profile. Enter the show dspfarm profile 1 command. Verify the status, number of supported sessions, and the list of supported codecs. When you go to Media Resources > Conference Bridge and click Find, you see HWCFB_HQ-x registered.

Task 3: Configure Meet-Me Conferences in Cisco Unified Communications Manager


In this task, you will configure Cisco Unified Communications Manager to support Meet-Me conferences.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3

In Cisco Unified Communications Manager Administration, go to Call Routing > Meet-Me Number/Pattern. Click Add New. In the Meet-Me Number Configuration window, enter the following parameters:

Meet-Me Number Configuration: 45XX Description: Meet-Me Range

66

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Step 4

Partition: Phones

Click Save.

Activity Verification
You have successfully completed this task when you attain these results:

You configured a Meet-Me number range in Call Routing > Meet-Me Number/Pattern. At Phone1-x, go off-hook and press the MeetMe softkey (use the More softkey to see all available softkeys). Dial a number from the MeetMe number range (for example, 4511). A Meet-Me conference will be opened. At all other phones (Phone2-x to Phone4-x), join the Meet-Me conference by dialing the Meet-Me number of the previously opened conference (4511).

Task 4: Manage MOH Audio Files


In this task, you will add audio files to Cisco Unified Communications Manager and use the audio translator to generate audio files that can be used by the MOH media resource.

Activity Procedure
Complete these steps: Upload an MOH Audio File Step 1 In the Cisco Unified Communications Manager Administration, go to Media Resources > MOH Audio File Management.
Step 2 Step 3

Click Upload File. Click Browse and choose a .wav file that is stored on your computer (for example, Windows XP Logon Sound.wav in C:\WINDOWS\Media\). Alternatively, ask your instructor for a MOH .wav file.
The filename must not contain spaces. Therefore you will have to copy the file first, rename it, and then refer to the renamed file.

Note

Step 4 Step 5 Step 6

Click Upload File. Wait until the Status changes to Upload Successful, then click Close. Update the browser page by navigating again to Media Resources > MOH Audio File Management. The uploaded file should now be shown in the file list and its status should be Translation Complete.
The upload of MOH files has to be performed per server that provides MOH services. In this lab, the IP Voice Media Streaming App service is only activated at the Publisher. However, it is recommended that you always upload all MOH files to all servers. This ensures that the MOH files are in sync on all servers of the clusters when the IP Voice Media Streaming App service is activated at another server at a later time,

Note

Step 7

Repeat Step 1 to Step 6 for the Subscriber by connecting to the Cisco Unified Communications Manager Administration web page using the IP address of the Subscriber in the URL (https://10.x.1.2/ccmadmin). After the file upload, close the browser window and connect back to the Cisco Unified Communications Manager Administration web page of the Publisher using the URL https://10.x.1.2/ccmadmin.
Lab Guide 67

2010 Cisco Systems, Inc.

Note

Uploading MOH files is the only task performed from the Cisco Unified Communications Manager Administration web page, which only applies to the server that is specified in the URL. Usually per-server configuration tasks are performed from the Cisco Unified Operating System Administration web page. In general, all configurations performed from the Cisco Unified Operating System Administration web page apply only to the server that is specified in the URL. All configurations performed from the Cisco Unified Communications Manager Administration web page apply to the whole cluster and not to an individual server (regardless which server IP address is used in the URL). Managing MOH files is the only exception. It has to be performed from the Cisco Unified Communications Manager Administration web page but only affects the server that is specified in the URL.

Add a New MOH Audio Source Step 8 Go to Media Resources > Music On Hold Audio Source and click Find.
Step 9 Step 10

You will see one entry (MOH Audio Stream Number 1the SampleAudioSource). Click Add New. Configure a second MOH audio source with the following parameters:

MOH Audio Stream Number: 2 MOH Audio Source File: <Name of previously uploaded file from Step 3> MOH Audio Source Name: Custom MOH Play continuously (repeat) check box: Activated

Step 11

Click Save.

Configure a Phone to Use the New Audio Source Step 12 Go to Device > Phone and click Find.
Step 13 Step 14 Step 15 Note

Enter the configuration for Phone1-x. Change the User Hold MOH Audio Source from <None> to 2-Custom MOH. Save your changes and reset the phone.
The default User Hold MOH Audio Source and Network Hold MOH Audio Source value is 1. By modifying the User Hold MOH Audio Source value at Phone1-x only, the default MOH file is played, unless the user at Phone1-x puts a call on hold.

Activity Verification
You have successfully completed this task when you attain these results:

You have uploaded a new MOH file in Media Resources > MOH Audio File Management. You have added a new MOH audio source for the uploaded MOH file. All phones use MOH audio source 1 for Network Hold events. MOH audio source 2 is used for User Hold at Phone1-x. All other phones use MOH audio source 1 for User Hold. Perform the following steps to verify your configuration:

68

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Step 1

Establish a call between Phone1-x and Phone2-x. Press the Hold softkey at Phone1x. The call to Phone1-x is put on user hold and you should hear the uploaded MOH file at Phone2-x. Press the Resume softkey at Phone1-x and keep the call open. Press the Hold softkey at Phone2-x. The call to Phone1-x is put on user hold and you should hear the default MOH file at Phone1-x. Press the Resume softkey at Phone2x and keep the call open. Press the Transfer softkey at Phone1-x and dial 2004. The call to Phone2-x is put on network hold and you should hear the default MOH file at Phone2-x. Accept the incoming call at Phone4-x. Press the Transfer softkey at Phone1-x and keep the transferred call (between Phone2-x and Phone4-x) open. Click the Hold button at the X-Lite application on PC-x (Phone4-x). No MOH is played at Phone2-x. This is because MOH is not supported for the third-party SIP phone. Click the Hold button again at Phone4-x to resume the call. Keep the call open. Press the Hold softkey at Phone2-x. The call to Phone4-x is put on user hold and you should hear the default MOH file at Phone4-x.
As you have seen during the activity verification, the MOH Audio Source is selected based on the configuration of the party that puts the other party on hold. The third-party SIP phone (Phone4-x) can listen to MOH when being held, but no MOH is played at a phone held by the third-party SIP phone.

Step 2

Step 3

Step 4

Step 5

Note

Task 5 (Optional): Configure Multicast MOH


In this task, you will configure Cisco Unified Communications Manager to use multicast MOH rather than unicast MOH.

Activity Procedure
Complete these steps: Enable Multicast MOH on Audio Sources Step 1 In the Cisco Unified Communications Manager Administration, go to Media Resources > Music On Hold Audio Source and click Find.
Step 2 Step 3

Enter the configuration of MOH Audio Stream Number 1 and check the Allow Multicasting check box. Click Save. Repeat the previous step for MOH Audio Stream Number 2.

Enable Multicast MOH at the MOH Server Step 4 Go to Media Resources > Music on Hold Server and click Find.
Step 5

You will see one MOH server per Cisco Unified Communications Manager server. They have been automatically configured during installation of the server. Their description is based on the name of the server as entered during installation. Click the MOH server that is currently registered (MOH_2, the MOH server running on the publisher) to enter the MOH Server Configuration window. In the Multicast Audio Source Information pane, check the Enable Multicast Audio Sources on this MOH Server check box. Verify that the Base Multicast IP Address is 239.1.1.1. Set the Increment Multicast On parameter to IP Address.
Lab Guide 69

Step 6 Step 7 Step 8

2010 Cisco Systems, Inc.

Step 9 Step 10 Step 11

Verify that the Max Hops parameter for Multicast Audio Source 1 and 2 is set to 2. Click Save and, in the pop-up window, click OK. Click Reset and, in the pop-up window, click Reset and then Close.

Enable Multicast Routing in the Network Step 12 Connect to your HQ-x router.
Step 13

Enter global configuration mode and apply the following commands:


ip multicast-routing interface FastEthernet0/0.1x1 ip pim sparse-dense-mode exit interface FastEthernet0/0.1x2 ip pim sparse-dense-mode exit

Note

You must enable multicast routing at both the incoming interface (Fa0/0.x01) and the outgoing interface (Fa0/0.1x2).

Activity Verification
You have successfully completed this task when you attain this result:

When MOH is played, multicast MOH, rather than unicast MOH, is used. To verify your configuration, you can watch the packets that are sent out on interface FastEthernet0/0.1x2. Perform the following steps for verification: At the HQ-x router, enter the following commands in global configuration mode:
access-list 101 permit udp host 10.x.1.1 239.1.1.0 0.0.0.255 access-list 101 permit udp host 10.x.1.1 any access-list 101 permit ip any any ! interface FastEthernet0/0.1x2 ip access-group 101 out exit ! copy running-config startup-config

Step 1

Note

This access list effectively permits all IP traffic. You can use it to see the match counts per access list line. In this lab, multicast MOH traffic will match the first access list line, and unicast MOH traffic will match the second access list line. All other IP traffic will match the third access list line.

Step 2

Use the show access-lists 101 command several times and look at the number of matches for each access list line:
Extended IP access list 101 10 permit udp host 10.x.1.1 239.0.0.0 0.255.255.255 (452 matches) 20 permit udp host 10.x.1.1 any (4 matches) 30 permit ip any any (8 matches)

70

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Note

At this stage, you should not see a significant increase in any access list line. Occasionally, the first access list line is incremented by about 50 matches per second, but not for longer than 10 to 15 seconds. This effect can be ignored for the verification of multicast MOH.

Step 3 Step 4

Keep your Telnet session to HQ-x open. Establish a call between Phone1-x and Phone2-x. Put the call on hold from any side. In your Telnet session to HQ-x, enter the show access-lists 101 command several times. Although you expect multicast MOH to be played, only the second access list line is incremented (by about 50 matches per second), while MOH is played at the held phone. Obviously the phones still use unicast MOH.
Occasionally, the first access list line is also incremented by about 50 matches per second, but not longer than 10 to 15 seconds. This effect can be ignored for the verification of multicast MOH.

Note

Note

Multicast MOH is not used because for multicast MOH, MRGs and MRGLs are required, and the Use Multicast for MOH Audio check box at the MRG must be checked. MRGs and MRGLs are implemented in the next task, so you will be able to verify your multicast MOH configuration only in the activity verification of the next task.

Task 6 (Optional): Implement Media Resources Access Control


In this task, you will assign media resources to MRGs, assign MRGs to MRGLs, and assign different MRGLs to different IP phones. This will allow selective media resource allocation per device (phone) and enable the use of multicast MOH.

Activity Procedure
Complete these steps: Configure MRGs
Step 1 Step 2

In Cisco Unified Communications Manager Administration, go to Media Resources > Media Resource Group and click Add New. In the Media Resource Group Configuration window. enter the following parameters:

Name: HW-CFB_mrg Description: IOS Hardware Conference Bridge

Step 3 Step 4 Step 5

From the Available Media Resources, choose the Cisco IOS hardware conference bridge HW-CFB_HQ-x. Click Save. Click Add New and enter following parameters:

Name: SW-CFB_mrg Description: Software Conference Bridge

Step 6 Step 7
2010 Cisco Systems, Inc.

From the Available Media Resources, choose the software conference bridge SWCFB_CUCM1-x. Click Save.
Lab Guide 71

Step 8

Click Add New and enter following parameters:


Name: Other-SW-MR_mrg Description: Other SW Media Resources: Annunciator, MoH, MTP

Step 9

From the Available Media Resources, choose ANN_2, MOH_2[Multicast] and MTP_2.
The software media resources that end with _3 are not active because the Cisco IP Voice Media Streaming App service has not been activated on the appropriate server (CUCM2-x). Therefore, there is no need to add them into any MRG.

Note

Step 10

Check the Use Multicast for MOH Audio (If at Least One Multicast MOH Resource Is Available) check box.
This setting is required to allow MOH servers that are part of the MRG to use multicasting (if enabled at the MOH servers).

Note

Step 11

Click Save. Go to Media Resources > Media Resource Group Lists and click Add New. In the Media Resource Group List configuration window, enter HW-SW_mrgl for the name. From the Available Media Resource Groups, choose all groups and make sure to order them as follows:

Configure MRGLs
Step 12 Step 13 Step 14

HW-CFB_mrg SW-CFB_mrg Other-SW-MR_mrg

Note

The hardware conference bridge should be used before the software conference bridge, so make sure that the HW-CFB_mrg is listed before the SW-CFB_mrg. Other media resource types (MOH server, annunciator, and MTP) are made available by adding the Other-SWMR_mrgl to the MRGL. The position of this MRG within the MRGL is not relevant because this is the only MRG that contains such types of media resources.

Step 15

Click Save.

Assign the MRGLs to Phones Step 16 Go to System > Device Pool and click Find and choose Default.
Step 17 Step 18 Step 19 Step 20

Change the Media Resource Group List from <None> to HW-SW_mrgl. Click Save. Click Reset and reset all devices using this device pool. From the Related Links, choose Dependency Records and click Go. You will see a record summary that indicates which device types (and their number) are using this device pool. Click Record Type Phone to see the list of phones that use this device pool. Note that Phone3-x uses a different device pool (SubPub).
2010 Cisco Systems, Inc.

Step 21

72

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Activity Verification
You have successfully completed this task when you attain these results:

From Phone1-x and from Phone2-x, you can initiate ad hoc and Meet-Me conferences. You cannot initiate ad hoc or Meet-Me conferences anymore from Phone3-x. Verify that the hardware conference media resource is used before the software conference media resource, by performing the following steps: End all active calls. From Phone1-x, set up a Meet-Me conference at number 4501. From Phone4-x, join the Meet-Me conference by dialing 4501. At Phone1-x, leave the Meet-Me conference by ending the call.
Phone4-x, the third-party SIP phone, cannot initiate conferences. However, by creating a Meet-Me conference from Phone2-x and dialing the Meet-Me number from Phone4-x, you put a Meet-Me conference in place, with Phone4-x as the only member (after Phone1-x drops out).

Step 1 Step 2

Note

Step 3

In a Telnet session to HQ-x, use the show dspfarm dsp active command to verify that the hardware conference bridge is used for the conference. Keep the call active at Phone4-x. Create another Meet-Me conference from Phone1-x, but this time use 4502 for the number. From Phone3-x, join the Meet-Me conference. At Phone1-x, leave the Meet-Me conference.
Phone3-x cannot create conferences because it does not have an MRGL assigned, and all media resources are put into MRGs. However, the Meet-Me conference was created by another phone, so a second conference is in place with Phone3-x as the only member (after Phone1-x drops out).

Step 4

Note

Step 5

Again, use the show dspfarm dsp active command at HQ-x to verify that the hardware conference bridge is also used for the second conference. Keep the call active at Phone3-x. From Phone1-x, call Phone2-x. At Phone2-x, create an ad hoc conference by adding PSTN-Phone-x to the call. Use any valid PSTN number (such as 9-555-1234) to call the PSTN phone. At HQ-x, use the show dspfarm dsp active command again to verify that this third conference does not use the hardware conference bridge (because the hardware conference media resource was configured for a maximum of two conference sessions). Because the ad hoc conference is operational, the software conference bridge must be used (as desired). End all calls.

Step 6

Step 7

Step 8

When dialing an invalid number (for example, 4444) from Phone1-x or Phone2-x, you will hear an annunciator message. At Phone3-x, you only hear the appropriate call progress tone. When Phone3-x is put on hold, only TOH is played at Phone3-x.

2010 Cisco Systems, Inc.

Lab Guide

73

Note

Phone3-x cannot listen to MOH because it does not have an MRGL assigned and all media resources (including the MOH server) are put into MRGs. Therefore, Phone3-x does not have access to any MOH server and TOH is played instead of MOH.

When Phone2-x or Phone3-x is put on hold, it hears MOH. Use the show access-lists 101 command at HQ-x to verify that multicast MOH is used this time.

74

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Lab 6-1: Configuring Cisco Unified Communications Manager Native Presence


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure presence-enabled speed dials on the three Cisco IP phones. Two of them (Phone2-x and Phone3-x) will also use presence-enabled call lists. Then you will apply presence policies to restrict presence subscriptions. After completing this activity, you will be able to meet these objectives:

Configure presence-enabled speed dials Configure Cisco Unified Communications Manager to support presence-enabled call lists Implement presence policies

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 6-1: Configuring Cisco Unified Communications Manager Native Presence


Phone1-x Phone2-x Phone3-x

DHCP

DHCP

DHCP

Each phone monitors status of other two phones.

10.x.2.0/24 PC-x HQ-x .101


DHCP .2

10.x.3.0/24

.101 .101

10.x.1.0/24

CUCM2-x

Enable presence subscriptions


.1

Implement presence policies

CUCM1-x

2010 Cisco Systems, Inc. All rights reserved.

CIPT1 v8.013

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC Cisco IP Phones

2010 Cisco Systems, Inc.

Lab Guide

75

Task 1: Configure Presence-Enabled Speed Dials


In this task, you will configure presence-enabled speed dials for phones Phone2-x and Phone3x. Each phone will watch the first line of the other.

Activity Procedure
Complete these steps: Configure Phone Button Templates for the IP Phones Step 1 Navigate to Device > Device Settings > Phone Button Template.
Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8

Choose the Standard 7965 SCCP Template and click Copy. Enter Standard 7965 SCCP Presence as the name of the new template and, for phone button 3, choose Speed Dial BLF. Click Save. Open the phone configuration for Phone2-x. Choose the Standard 7965 SCCP Presence Phone Button Template and click Save. Click the Add a new BLF SD link next to phone line 3. Enter 2003 in the Destination field and click Save. Repeat Steps 4 through 7 for Phone3-x but enter 2002 at the Destination field.

Verify the Need for Presence CSS Step 9 Write down the partitions that are assigned to the first directory numbers of the following phones:
Step 10

Phone2-x: _____________________ Phone3-x: _____________________

Place calls between phones and verify that you do not see presence information on the corresponding presence-enabled speed dials.
You will not see presence information because the watched directory numbers are in partitions but no subscribe CSS is applied to the IP phones.

Note

Implement Subscribe CSS Step 11 Create a CSS called Presence_css, which includes all partitions that were discovered in Step 9.
Step 12

Open the phone configuration for phones Phone2-x and Phone3-x, scroll down to the Protocol Specific Information field and assign the previously created CSS as a SUBSCRIBE Calling Search Space. Reset both phones. Place calls between phones and verify that you now see presence information on the corresponding presence-enabled speed dials.
When implementing presence in an environment that already has partitions in use (because of calling-privilege implementation), presence is also affected by these partitions. Therefore, subscribe CSS must be assigned even if no restrictions should be applied to presence.

Step 13 Step 14

Note

76

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Activity Verification
You have completed this task when you attain these results:

Phone2-x and Phone3-x see accurate presence information at the presence-enabled speed dials.

Task 2: Implement Presence-Enabled Call Lists


In this task, you will configure presence-enabled call lists.
Note The presence-enabled call lists feature is not available at older Cisco Unified IP phone models such as the Cisco Unified IP Phone 7940 and 7960 models.

Activity Procedure
Complete these steps: Enable Presence-Enabled Call Lists Step 1 Place a call from each phone to the other two phones and do not answer the call.
Step 2 Step 3 Step 4 Step 5 Step 6

Go to System > Enterprise Parameters and enable the BLF for Call Lists enterprise parameter in Cisco Unified Communications Manager Administration. Click Save and Reset. On the Phone2-x and Phone3-x, press the Directory button and choose Missed Calls. You should see the presence status also on the call lists. Press the Directory button at the Phone1-x and choose Missed Calls. Observe that presence information is not available to this phone. This is because you have not configured a Subscribe CSS for this phone. Assign the Presence_css as the Subscribe CSS for Phone1-x. Repeat Step 6 for Phone1-x and verify that presence-enabled call lists are now visible for Phone1-x.
Presence-enabled call lists also require the subscribe CSS when the watched directory numbers are in partitions. A subscribe CSS was already assigned to all phones, in the previous task.

Step 7 Step 8

Note

Activity Verification
You have completed this task when you attain this result:

At Phone1-x, Phone2-x and Phone3-x, you can view presence information in call lists.

Task 3 (Optional): Configure Presence Policies


In this task, you will limit presence visibility by implementing presence policies. You will configure presence groups to control presence visibility for call lists.

2010 Cisco Systems, Inc.

Lab Guide

77

Activity Procedure
Complete these steps: Implement Presence Policies In this section, you will apply the following presence policies:

The manager phone (Phone3-x) should be able to see presence-enabled call list information for all other phones. All other phones will have access to presence-enabled call-list information between each other but not for the manager phone. The employee phone (Phone2-x) will still be able to use the presence-enabled speed dial.

Follow these steps to implement presence policies for speed dials:


Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10

Navigate to System > Presence Group and click Add New. At the Name field enter Manager_pg. Select the Standard Presence group, choose Allow Subscriptions from the Subscription Permission drop-down menu, and click Save. In the Related Links menu, leave Back to Find/List selected and click Go. Click Find and open the Standard Presence Group configuration. Select Manager_pg and choose Disallow Subscriptions from the Subscription Permission drop-down menu, and click Save. Open the Configuration page for Phone3-x. Choose Line [1]2003 in Manager-Phones. At the Line Configuration window for line 2003, choose Manager_pg from the Presence Group drop-down menu. Click Save and Reset.

Activity Verification
You have completed this task when you attain this result:

Presence subscriptions work as described in the activity procedure.

78

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Lab 6-2: Configuring Cisco Unified Mobility


Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will implement Mobile Connect (Tasks 1 to 4) and MVA (Tasks 5 to 7). After completing this activity, you will be able to meet these objectives:

Add the Mobility softkey to IP phones Associate an end-user account with the IP phone and enable the use of mobility Configure remote destination profiles and remote destinations Enable MVA Configure Cisco Unified Mobility media resources Configure the Cisco IOS gateway for Cisco Unified Mobility

Visual Objective
The figure illustrates what you will accomplish in this activity.

Lab 6-2: Configuring Cisco Unified Mobility


Phone1-x Phone2-x Phone3-x

Configure Cisco Unified Mobility for Phone3-x.


PSTN

DHCP

DHCP

DHCP

10.x.250.201/32 PSTN

10.x.2.0/24 PC-x HQ-x


DHCP .2 .101

10.x.3.0/24

.101 .101

10.x.1.0/24

CUCM2-x

.1

CUCM1-x

Implement call application providing Mobile Voice Access through IVR VXML.

Allow remote destinations (mobile phone, home office phone) to be used for office calls.

2010 Cisco Systems, Inc. All rights reserved.

CIPT1 v8.014

Required Resources
These resources and equipment are required to complete this activity:

Cisco Unified Communications Manager cluster Student PC Cisco IP Phones Cisco IOS gateway (MGCP and H.323) PSTN with PSTN phone
Lab Guide 79

2010 Cisco Systems, Inc.

Task 1: Add the Mobility Softkey to IP Phones


In this task, you will configure a softkey template to include the Mobility softkey and apply the softkey template to an IP phone.

Activity Procedure
Complete these steps: Configure a Softkey Template with the Mobility Softkey Step 1 In Cisco Unified Communications Manager Administration, navigate to the Device > Device Settings > Softkey Template menu and click Find.
Step 2 Step 3 Step 4 Step 5 Step 6

Locate and click the Copy icon to the right of the Standard User. Enter the name Standard User Mobility. Enter Mobility Softkey Template for the Description and click Save. From the Related Links, choose Configure Softkey Layout and click Go. Verify that On Hook is chosen in the Select a Call State to Configure drop-down menu. Click the Mobility entry in the Unselected Softkeys pane and move it to the Selected Softkeys pane by using the arrow link. Save the configuration. Repeat the previous steps to add the Mobility softkey to the Connected call state.

Step 7 Step 8

Assign the Softkey Template to the IP Phone Step 9 Navigate to Device > Phone and click Find.
Step 10 Step 11 Step 12 Step 13

Choose Phone3-x. Choose Standard User Mobility from the Softkey Template drop-down menu. Click Save and click OK in the pop-up window. Reset the phone.

Activity Verification
You have completed this task when you attain these results:

Press the Mobility Softkey on Phone3-x. The You are not a valid Mobile User error message should be displayed.

Task 2: Associate an End User Account with the IP Phone and Enable the Use of Mobility
In this task, you will configure an existing end-user account for Cisco Unified Mobility and associate the user with an office phone.

Activity Procedure
Complete these steps: Configure an End User for Device Mobility Step 1 Navigate to the User Management > End User and click Find.
Step 2 Step 3

Choose user User3. In the Mobility Information area, check the Enable Mobility check box.
2010 Cisco Systems, Inc.

80

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Step 4 Step 5

Change the Remote Destination Limit to 1. Click Save.

Configure the Office Phone to Be Owned by the End User Step 6 Navigate to Device > Phone and click Find.
Step 7 Step 8 Step 9 Step 10

Choose Phone 3-x. In the Device Information pane choose User3 from the Owner User ID drop-down menu. Click Save and click OK in the pop-up window. Reset the phone.

Activity Verification
You have completed this task when you attain these results:

End-user User3 is enabled for Device Mobility and assigned to Phone3-x (that is, the office phone of the user) as the owner. Press the Mobility Softkey on Phone3-x. The No Mobile Remote Destination found error message should be displayed.

Task 3: Configure Remote Destination Profiles and Remote Destinations


In this task, you will configure remote destination profiles and remote destinations. The remote destination profile is a virtual phone that shares its line with the office phone of the user. The remote destination profile represents the associated remote destinations (that is, PSTN numbers such as mobile phone or home phone).

Activity Procedure
Complete these steps: Configure a Remote Destination Profile Step 1 Navigate to Device > Device Settings > Remote Destination Profile and click Add New.
Step 2

Enter the following parameters:


Name: User3-rdp Description: RDP of User3 User ID: User3 Device Pool: Default Calling Search Space: Phones_css Privacy: On Rerouting Calling Search Space: Phones_css

2010 Cisco Systems, Inc.

Lab Guide

81

Note

The Rerouting Calling Search Space parameter is the CSS that is used for ringing the remote destination when a call is received at the office phone. The parameter is also used for handing calls that are active at the office phone to a remote destination. The Calling Search Space parameter is the device CSS of the virtual phone that represents the remote destinations. In other words, this CSS is used when placing outgoing enterprise calls from a remote destination. The MVA feature is used only later in this lab exercise (Tasks 5 to 7).

Step 3 Step 4 Step 5 Step 6

Check the Ignore Presentation Indicators (internal calls only) check box. Click Save. Click Line [1]Add a New DN. At the Directory Number Configuration window, enter 2003 for the Directory Number. Then click in any other input field so that the configuration of this directory number is loaded. Choose the Manager-Phones partition. Enter 52x5553XXX in the External Phone Number Mask. Click Save. Verify that User3-rdp shows up at the Associated Devices section. From the Related Links, choose Configure Device (User3_rdp) and click Go, to return to the Remote Destination Profile Configuration window.

Step 7 Step 8 Step 9 Step 10 Step 11

Configure a Remote Destination Step 12 At the Associated Remote Destinations pane, click Add a New Remote Destination.
Step 13 Step 14 Step 15 Note

Enter the name User3_home. Enter the Destination Number 916065554444. Check the Mobile Phone check box.
This parameter allows or disallows calls that are active at the office phone to be handed over to the remote destination.

Step 16 Note

Verify that the Enable Mobile Connect check box is checked.


This parameter allows or disallows the remote destination to ring when a call is received at the office phone.

Step 17 Step 18 Step 19 Step 20 Step 21

Click Save and click OK in the pop-up window. In the Association Information pane check the check box at the right of Line [1] 2003 in Manager-Phones. Click Save and click OK in the pop-up window. Navigate to Call Routing > Class of Control > Calling Search Space and select the To-Phones_css. Add the Manager Phones Partition to this Calling Search Space and click Save.

82

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Note

For the verification of this lab, you need to allow calls from the PSTN to the Manager phone (Phone3-x).

Activity Verification
You have completed this task when you attain these results:

Verify that both the office phone and the PSTN phone ring when internal calls are made to Phone3-x: From Phone2-x, make a call to 2003. The call should be presented to Phone3-x line 1 and to the PSTN phone (at line 2). Answer the call on the PSTN phone. Look at the line 1 button on Phone3-x. Note the color is red, indicating that a call is active at a remote destination on the shared line 2003. Hand the call over to the office phone by ending the call at the PSTN phone and then pressing the Resume softkey on Phone3-x. End the call.

Step 1 Step 2 Step 3 Step 4 Step 5 Step 6

Verify that calls from the PSTN phone line 2 (remote destination) are presented as calls from the office phone when calling internal directory numbers: At the PSTN phone, press the National button to place a call with a long distance calling number, and dial 152x5553002. Verify that the call is presented with the internal number of Phone3 (2003) at the receiving phone (Phone2-x). While Phone2-x is ringing, look at the line 1 button on Phone3-x. Note that the color is red, indicating that the remote destination has a call. End the call on the PSTN phone.

Step 1 Step 2 Step 3

Verify that calls that are made from PSTN phones to Phone3-x will ring at 2003 and at the remote destination (PSTN phone line 2). Verify that the remote phone (PSTN phone line 2) is showing the caller ID of the PSTN phone that called Phone3-x. From the PSTN phone line 1, make a call to Phone3-x (152x5553003). The call should be presented to Phone3-x line 1 and to the PSTN phone (at line 2). Check the caller ID of the call ringing at the PSTN phone line 2. The caller ID should be the number of the PSTN phone line 1. End the call without answering.
In many countries, you are not allowed to set the calling number of outgoing PSTN calls to a number that is different from your actual PSTN number. Therefore, the preservation of the calling number for mobile connect calls depends on legal regulations or policies of the PSTN provider.

Step 10 Step 11 Step 12 Step 13 Note

Verify that the office phone can hand an answered call over to the PSTN phone: From Phone2-x, make a call to 2003. The call should be presented to Phone3-x line 1 and PSTN phone line 2. Answer the call at Phone3-x.
Lab Guide 83

Step 1 Step 2
2010 Cisco Systems, Inc.

Step 3 Step 4 Step 5 Step 6 Step 7 Step 8

Use the More softkey to navigate to the Mobility softkey. Press the Mobility softkey. Press the Select softkey to send the call to the PSTN phone. Answer the call on the PSTN phone. Keep the call active between Phone2-x and the PSTN phone, and make a call from Phone3-x to 2001, answer the call on Phone1-x. Phone2, which is connected to the PSTN phone, and Phone1, which is connected to Phone3, should both show a connection with 2003. Terminate all calls.

Task 4: Configure Ring Schedules and Access Lists for Remote Destinations
In this task, you will configure a ring schedule to ring the remote destination only during a specified time range. Further calls from PSTN phone line 9 (emergency) will be blocked even during the allowed time schedule.

Activity Procedure
Complete these steps: Configure an Access List Step 1 Open the User Web Page (https://10.x.1.1/ccmuser) and log on User3
Step 2 Step 3 Step 4 Step 5 Step 6

Navigate to User Options > Mobility Setting > Access List and click Add New. Enter the Access List Name ACL911. Make sure the Blocked radio button is selected and click Save. Click Add Member and enter 911. Click Save.

Configure a Ring Schedule for the Remote Destination Step 7 Navigate to User Options > Mobility Setting > Remote Destinations and click Find.
Step 8 Step 9 Step 10

Open the configured remote destination. At the Ring Schedule Pane, choose the As Specified Below radio button. Check all check boxes from Monday to Friday and specify 09:00 to 18:00 as begin and end times.

Apply the Access List to the Remote Destination Step 11 At the When receiving a call during the above ring schedule pane, choose the Do not ring this destination if caller is in radio button and choose the ACL911 access list from the drop-down menu.
Step 12

Click Save.

Activity Verification
You have completed this task when you attain these results:
Step 1

Verify that the current date and time that is displayed on Phone3-x is within the specified schedule (Monday through Friday, 9:00 to 18:00).
2010 Cisco Systems, Inc.

84

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9

From the PSTN phone line 1, call Phone3-x (152x5553003). The call should be presented to Phone3-x line 1 and to the PSTN phone (at line 2). From the PSTN phone line 6 (emergency), call Phone3-x (152x5553003). The call should be presented to Phone3-x line 1 but not to the PSTN phone line 2. Navigate to User Options > Mobility Setting > Remote Destinations and click Find. Choose the configured remote destination and set the Ring Schedule of the current weekday to a value outside the current time (for example, 23:00 to 23:05). Click Save. Repeat Steps 2 and 4. The remote destination (PSTN Phone line 2) should never ring.

Cleanup
To prepare for future labs, follow these steps to re-enable the remote destination at all times.
Step 1

At the Remote Destination Configuration select All the time at the Ring Schedule pane and Alway ring this destination at the When receiving a call during the above ring schedule pane. Click Save.

Step 2

Task 5: Enable MVA


In this task, you will activate the Cisco Unified Mobile Voice Access Service feature service. You will configure Cisco Unified Mobility service parameters to enable the MVA feature globally, and then you will allow individual end users to use MVA.

Activity Procedure
Complete these steps: Activate the Cisco Unified Mobile Voice Access Service Step 1 In Cisco Unified Serviceability, navigate to Tools > Service Activation.
Step 2 Step 3 Note

Select the 10.x.1.1 server and check the Cisco Unified Mobile Voice Access Service check box. Click Save.
The Cisco Unified Mobile Voice Access Service can be activated only on the publisher server.

Configure Cisco Unified Mobility Service Parameters In the following steps, you will enable Enterprise Feature Access and write down the corresponding feature access codes. Then you will enable MVA globally.
Step 4 Step 5 Step 6 Step 7

Navigate to System > Service Parameters. Choose server 10.x.1.1 and service Cisco CallManager. Locate the Clusterwide Parameters (SystemMobility) section. Set the Enable Enterprise Feature Access parameter to True.

2010 Cisco Systems, Inc.

Lab Guide

85

Note

Enterprise Feature Access allows Cisco Unified Communications Manager features such as hold, resume, transfer, and conference to be controlled from a remote phone by using DTMF tones.

Step 8

Record the Clusterwide Parameters (SystemMobility) Enterprise Feature Access Codes for the following features:
Feature Access Code

Feature Hold Exclusive Hold Resume Transfer Conference Step 9 Step 10

Set the Enable Mobile Voice Access and the Enable Enterprise Feature Access parameter to True. Save the configuration.

Configure End Users to Be Allowed to Use MVA Step 11 Navigate to the User Management > End User and click Find.
Step 12 Step 13 Step 14

Choose user User3. In the Mobility Information area, check the Enable Mobile Voice Access check box. Click Save.

Activity Verification
You have completed this task when you attain these results:

In Cisco Unified Serviceability under Tools > Control CenterFeature Services, the Cisco Unified Mobile Voice Access Service is activated and running. The Service Parameters have been updated under System > Service Parameters, as described in the activity procedure. End-user User1 is configured to be allowed to use MVA.

Task 6: Configure Cisco Unified Mobility Media Resources


In this task, you will configure the Cisco Unified Mobility media resources that will be used by MVA.

Activity Procedure
Complete these steps:
Step 1 Step 2 Step 3

Navigate to Media Resources > Mobile Voice Access. Enter 2999 for the Mobile Voice Access Directory Number. Choose Phones for the Mobile Voice Access Partition.

86

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Step 4 Step 5

Choose the English United States locale in the list of Available Locales and move it to the Selected Locales by using the arrow link. Save the configuration.

Activity Verification
You have completed this task when you attain this result:

The resource is configured under Media Resources > Mobile Voice Access.

Task 7: Configure the Cisco IOS Gateway for Cisco Unified Mobility
In this task, you will configure the Cisco IOS gateway with a call application that allows PSTN calls to be placed from the remote phone as if they originated from the office phone. Remember that your T1/E1 PSTN connection is MGCP-controlled. To direct calls to the IVR application, you will need to send calls that are received on Cisco Unified Communications Manager via the MGCP-controlled interface back to the gateway using H.323 signaling (hairpinning).

Activity Procedure
Complete these steps: Configure H.323 Gateway Functionality for the IVR Application and Hairpinning Step 1 Log in to the HQ-x gateway and enter the following commands in configuration mode.
voice service voip allow-connections h323 to h323 exit application service MVA http://10.x.1.1:8080/ccmivr/pages/IVRMainpage.vxml exit

Configure a POTS Dial-Peer for the MVA Number Step 2 Configure an incoming VoIP dial peer for the MVA number (2998) and associate the IVR call application with it.
dial-peer voice 2998 voip service MVA incoming called-number 2998 codec g711ulaw dtmf-relay h245-alphanumeric no vad exit

Configure a VoIP Dial-Peer to the MVA Media Resource Step 3 Configure a VoIP dial peer to enable the call application that is running in Cisco IOS Software to contact the MVA media resource in Cisco Unified Communications Manager.
dial-peer voice 2999 voip destination-pattern 2999

2010 Cisco Systems, Inc.

Lab Guide

87

Note

The destination pattern must match the MVA directory number that is configured at the MVA media resource. The pattern does not need to match the last digits of the PSTN number that is used for MVA (52x5553998 in this case).

session target ipv4:10.x.1.1 codec g711ulaw dtmf-relay h245-alphanumeric no vad exit


Step 4

Save the configuration to NVRAM.

Add the HQ-x Gateway in Cisco Unified Communications Manager as H.323 Gateway Step 5 Navigate to Device > Gateway and click Add New.
Step 6 Step 7

Choose H.323 Gateway from the Gateway Type drop-down menu and click Next. Enter the following parameters:

Device Name: 10.x.1.101 Description: HQ-x (for Hairpinned H.323MVA calls) Device Pool: Default Calling Search Space (Inbound Calls): To-Phones_css

Step 8 Step 9

Click Save and Reset. Add a new route pattern with the following attributes:

Route Pattern: 2998 Route Partition: Phones Gateway/Route List: 10.x.1.101 Provide Outside Dial Tone: Uncheck

Step 10

Click Save.

Check Whether the Remote Destination Is Recognized at the H.323 Gateway It is important to provide the correct calling number to the IVR application that is configured on the H.323 gateway. Similar to Mobile Connect, MVA needs to detect that the call is coming from a configured remote destination. If a remote destination cannot be detected, the MVA caller has to authenticate to MVA by entering a valid remote destination number and the PIN of the associated user. If a remote destination is detected, only the PIN has to be entered. Check if the remote destination is recognized by performing the following steps:
Step 11 Step 12 Step 13

From PSTN phone line 2, dial 152x5553998. Listen to the IVR script. You will be prompted to enter your remote destination number (916065554444) and your PIN (12345). End the call.

88

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Note

In this case, the remote destination was not recognized and therefore the remote destination number had to be entered before being prompted for the PIN. This happens because all calls from the PSTN arrive at Cisco Unified Communications Manager through the MGCPcontrolled interface. If a call arrives at Cisco Unified Communications Manager and originates from a configured remote destination number, the calling number is transformed to the office extension (2003) by Mobile Connect. When sending the MVA call received from the remote destination to the IVR application, the application is no longer able to recognize the received call as a call from a remote destination because the calling number is 2003 instead of the actual remote destination number. As a consequence, the MVA user is prompted to enter a valid remote destination number before being asked for the PIN.

Configure Digit Manipulation to Provide Correct Calling Number Information to the IVR Application In order to send the original calling number of the remote destination to the IVR call application, you will configure voice translation rules at the H.323 gateway. The voice translation rule will match on the four-digit directory number of the office phone and translate this internally used office number to the associated remote destination number.
Step 14

Log in to the HQ-x gateway and enter the following commands in global configuration mode
! voice translation-rule 1 rule 1 /^2003$/ /916065554444/ exit ! voice translation-profile mva-vtr translate calling 1 exit ! dial-peer voice 2998 voip translation-profile incoming mva-vtr end !

Activity Verification
You have completed this task when you attain these results:

An outgoing PSTN call can be placed from the remote phone but appears to be initiated from the office phone. From PSTN phone line 2, dial 152x5553998. Listen to the IVR script prompt. The remote destination number (PSTN 916065554444) is recognized, and only the PIN is requested from the IVR script. Enter the PIN 12345 followed by #, when prompted by the IVR script. Listen to the IVR script prompt. Choose option 1 to initiate a call. from the remote phone to a PSTN destination. that looks like a call from the office phone.

Step 1 Step 2 Step 3 Step 4

2010 Cisco Systems, Inc.

Lab Guide

89

Step 5 Step 6

Enter a PSTN directory number as it would be entered from Phone3-x (for example, 9-911), followed by #. Verify that the incoming call that is received at the PSTN phone presents the full directory number of Phone3-x. The call should be received at the PSTN phone at line 6, the emergency line. End the call.

Step 7

Make a call from a nonremote destination and verify that the remote destination is unknown. From PSTN phone line 1, dial 152x5552998. The IVR script should now prompt for the remote destination. Enter your remote destination 916065554444 and then your PIN, as prompted by the script. Place a call to a PSTN destination (for example, 9-911). The call should be received at the PSTN phone line 5 (emergency); the calling number should be 51x5553003. End the call. From PSTN phone line 1, dial 152x5552998. Log in by entering your remote destination number and PIN. Place a call to an internal phone (2001). Verify that the call is received at Phone1-x, with the internal directory number of Phone3-x (2003) as the calling number. End the call.

Step 1 Step 2 Step 3 Step 4

Make a call from a nonremote destination to an internal phone number.

Step 5 Step 6 Step 7 Step 8 Step 9

Dial the MVA number again, and activate (option 2) and deactivate (option 3) Mobile Connect capabilities via the TUI. From PSTN phone line 2, dial 152x5552998. Log in by specifying your PIN, and choose option 3 to disable mobility for this remote location. End the call. From Phone2-x, call 2003. Note that the call is not sent to the remote destination. End the call. From PSTN phone line 2, dial 152x5552998. Log in by specifying your PIN, and choose option 2 to re-enable mobility for this remote location. End the call. From Phone2-x, call 2003. Note that the call is sent again to the remote destination. End the call.

Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10

Dial the MVA number and use Enterprise Feature Access to place a call on hold and to resume the call. From PSTN phone line 2, dial 152x5552998. Log in by specifying your PIN.
2010 Cisco Systems, Inc.

Step 1 Step 2

90

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

Step 3 Step 4 Step 5

Make a call to an internal phone (Phone2-x). Accept the call at Phone2-x. Dial Feature Access Code *81 to place the call on hold. Phone2-x should play MOH. At Phone3-x, the display indicates that the call at the remote phone has been put on hold. Use Feature Access Code *83 to resume the call.

Step 6

2010 Cisco Systems, Inc.

Lab Guide

91

Answer Key
The correct answers and expected solutions for the activities that are described in this guide appear here.

Lab 2-1: Configuring Cisco Unified Communications Manager Initial Settings


The solution is part of the activity procedure and verification.

Lab 2-2: Managing User Accounts in Cisco Unified Communications Manager


The solution is part of the activity procedure and verification.

Lab 3-1: Implementing IP Phones


The solution is part of the activity procedure and verification.

Lab 4-1: Implementing PSTN Gateways


When you complete this activity, your new HQ-x router configuration will be similar to the results here, with differences that are specific to your device or pod:
! card type t1 0 0 network-clock-participate wic 0 ! isdn switch-type primary-ni ! controller T1 0/0/0 framing esf linecode b8zs clock source line pri-group timeslots 1-8,24 service mgcp description to PSTN
Note Some of these commands are default commands and therefore may not be shown.

! interface Serial0/0/0:23 no ip address encapsulation hdlc isdn switch-type primary-ni isdn incoming-voice voice isdn bind-l3 ccm-manager no cdp enable ! voice-port 0/0/0:23 ! ccm-manager redundant-host 10.2.1.2

92

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

ccm-manager mgcp no ccm-manager fax protocol cisco ccm-manager music-on-hold ccm-manager config server 10.2.1.1 no ccm-manager config server
Note The no ccm-manager config server command is a default command and therefore is not shown.

! mgcp mgcp call-agent 10.2.1.1 2427 service-type mgcp version 0.1 mgcp rtp unreachable timeout 1000 action notify mgcp modem passthrough voip mode nse mgcp package-capability rtp-package mgcp package-capability sst-package mgcp package-capability pre-package no mgcp package-capability res-package no mgcp timer receive-rtcp mgcp sdp simple mgcp fax t38 ecm mgcp fax t38 inhibit mgcp behavior g729-variants static-pt ! mgcp profile default !

Lab 4-2: Configuring Cisco Unified Communications Manager Call-Routing Components


The solution is part of the activity procedure and verification.

Lab 4-3: Implementing Digit Manipulation


The solution is part of the activity procedure and verification.

Lab 4-4: Implementing Calling Privileges in Cisco Unified Communications Manager


The solution is part of the activity procedure and verification.

Lab 4-5: Implementing Call Coverage in Cisco Unified Communications Manager


The solution is part of the activity procedure and verification.

Lab 5-1: Implementing Media Resources


When you complete this activity, your new HQ-x router configuration will be similar to the results here, with differences that are specific to your device or pod:

2010 Cisco Systems, Inc.

Lab Guide

93

! ip multicast-routing ! voice-card 0 dspfarm dsp services dspfarm ! interface FastEthernet0/0.1x1 description HQ-x Servers encapsulation dot1Q 1x1 ip address 10.x.1.101 255.255.255.0 ip pim sparse-dense-mode ! interface FastEthernet0/0.1x2 description HQ-x Phones encapsulation dot1Q 1x2 ip address 10.x.2.101 255.255.255.0 ip access-group 101 out ip helper-address 10.x.1.1 ip pim sparse-dense-mode ! sccp local FastEthernet0/0.1x1 sccp ccm 10.x.1.2 identifier 2 version 7.0 sccp ccm 10.x.1.1 identifier 1 version 7.0 sccp ! sccp ccm group 1 associate ccm 1 priority 1 associate ccm 2 priority 2 associate profile 1 register HW-CFB_HQ-2 ! dspfarm profile 1 conference codec g711ulaw codec g711alaw codec g729ar8 codec g729abr8 codec g729r8 codec g729br8 maximum sessions 2 associate application SCCP ! access-list 101 permit udp host 10.x.1.1 239.1.1.0 0.0.0.255 access-list 101 permit udp host 10.x.1.1 any access-list 101 permit ip any any !
Note The x has to be replaced by your pod number.

94

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

Lab 6-1: Configuring Cisco Unified Communications Manager Native Presence


The solution is part of the activity procedure and verification.

Lab 6-2: Configuring Cisco Unified Mobility


When you complete this activity, your new HQ-x router configuration will be similar to the results here, with differences that are specific to your device or pod:
! voice service voip allow-connections h323 to h323 ! voice translation-rule 1 rule 1 /^2003$/ /916065554444/ ! voice translation-profile mva-vtr translate calling 1 ! application service MVA http://10.x.1.1:8080/ccmivr/pages/IVRMainpage.vxml ! dial-peer voice 2998 voip translation-profile incoming mva-vtr service MVA incoming called-number 2998 dtmf-relay h245-alphanumeric codec g711ulaw no vad ! dial-peer voice 2999 voip destination-pattern 2999 session target ipv4:10.x.1.1 dtmf-relay h245-alphanumeric codec g711ulaw no vad !
Note The x has to be replaced by your pod number.

2010 Cisco Systems, Inc.

Lab Guide

95

96

Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v8.0

2010 Cisco Systems, Inc.

You might also like