CIPT160LG Secured PDF

CIPT1
Implementing Cisco
Unified Communications
IP Telephony Part 1
Version 6.0
Lab Guide
Editing, Production, and Web Services: 02-15-08
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.
The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,
for the sole use by Cisco employees for personal study. The files or printed representations may not be
used in commercial training, and may not be distributed for purposes other than individual self-study.
Table of Contents
Lab Guide
Overview
1
Outline
1
Lab 1-1: Cisco Unified Communications Manager Installation and Upgrade Discovery
2
Activity Objective
2
Visual Objective
2
Required Resources
2
Job Aids
3
Task 1: Install Cisco Unified Communications Manager Publisher
3
Task 2: Install Cisco Unified Communications Manager Subscriber
16
Lab 2-1: Exploring Cisco Unified Communications Manager Administration Options
29
Activity Objective
29
Visual Objective
29
Required Resources
29
Job Aids
30
Task 1: Access the Cisco Unified Communications Manager Administration Window
30
Task 2: Understanding the Cisco Unified Serviceability System
32
Task 3: Understanding the Platform Administration Web GUI
33
Task 4: Understanding Platform Administration CLI Access
35
Lab 2-2: Configuring Cisco Unified Communications Manager Initial Settings
37
Activity Objective
37
Visual Objective
37
Required Resources
38
Job Aids
38
Task 1: Upload the License File
38
Task 2: Eliminate DNS Reliance
39
Task 3: Manage Network and Feature Services
40
Task 4: Configure Cisco Unified Communications Manager to Provide DHCP Services
42
Task 5: Configure Cisco Unified Communications Manager Enterprise and Service Parameters
43
Lab 2-3: Managing User Accounts in Cisco Unified Communications Manager
45
Activity Objective
45
Visual Objective
45
Required Resources
45
Job Aids
46
Task 1: Managing User Accounts Using the Administration GUI
46
Task 2: Managing User Accounts Using BAT
49
Task 3: Configure Cisco Unified Communications Manager to Use LDAP for User Provisioning 52
Task 4: Configure Cisco Unified Communications Manager LDAP Authentication
55
Lab 3-1: Configuring Voice VLANs
57
Activity Objective
57
Visual Objective
57
Required Resources
57
Command List
58
Job Aids
58
Task 1: Discovering the Cisco Catalyst IOS Switch Configuration
60
Task 2: Configuring Data and Voice VLANs
61
Lab 3-2: Implementing IP Phones
65
Activity Objective
65
Visual Objective
65
Required Resources
66
Job Aids
66
Task 1: Configuring System Parameters
66
Task 2: Add IP Phones Using Auto-Registration
69
Task 3: Manually Add and Configure an IP Phone
70
Task 4: Prepare the Cisco Unified Communications Manager BAT for Adding Cisco IP Phones 71
Task 5: Insert IP Phones into the Cisco Unified Communications Manager Database Using BAT
74
Task 5: Insert IP Phones into the Cisco Unified Communications Manager Database Using BAT
74
Task 6: Configure Cisco Unified Communications Manager to Support a Third-Party SIP
Softphone
75
Task 7: Enable Digest Authentication for a Third-Party SIP Softphone
76
Lab 3-3: Hardening IP Phones
79
Activity Objective
79
Visual Objective
79
Required Resources
79
Command List
80
Job Aids
80
Task 1: Discovering IP Phone Default Behavior
80
Task 2: Disabling Default Phone Settings
82
Lab 4-1: Implementing MGCP Gateways
85
Activity Objective
85
Visual Objective
85
Required Resources
85
Command List
86
Job Aids
86
Task 1: Configure an MGCP Gateway Using T1 PRI to the PSTN in Cisco Unified
Communications Manager
87
Task 2: Configuring a Cisco IOS Gateway for MGCP
88
Task 3: Configuring a Route Pattern Toward the MGCP Gateway Trunk
89
Lab 4-2: Configuring Cisco Unified Communications Manager Call Routing Components
91
Activity Objective
91
Visual Objective
91
Required Resources
91
Command List
92
Job Aids
92
Task 1: Configure a Redundant MGCP Gateway for Additional PSTN Access
92
Task 2: Configuring a Route Plan Using MGCP Gateways that Includes a Route Group, Route
List, and Route Pattern
93
Task 3: Enable DNA and Use It for Dial Plan Verification
95
Lab 4-3: Implementing Digit Manipulation
98
Activity Objective
98
Visual Objective
98
Required Resources
98
Job Aids
99
Task 1: Configure Cisco Unified Communications Manager to Strip Access Codes Used for
Called Numbers on Outgoing Calls
99
Task 2: Configure Cisco Unified Communications Manager to Extend Calling Numbers in
Outgoing Calls to Fully Qualified PSTN Numbers
100
Task 3: Configure Cisco Unified Communications Manager to Reduce the Called E.164 PSTN
Number of Incoming Calls to Directory Numbers
101
Task 4: Configure Cisco Unified Communications Manager to Prefix an Access Code to Calling
Numbers on Incoming Calls
102
Lab 4-4: Implementing Calling Privileges in Cisco Unified Communications Manager
104
Activity Objective
104
Visual Objective
104
Required Resources
104
Job Aids
105
Task 1: Configuring Partitions and CSSs
107
Task 2: Implement CoS for Internal Calls
108
Task 3: Implement CoS for Incoming PSTN Calls
109
Task 4: Implement CoS for Outgoing PSTN Calls
110
Task 5: Implement Time-of-Day-Based CoS
111
Task 6: Implement Forced Authorization Codes
113
Lab 4-5: Implementing Call Coverage in Cisco Unified Communications Manager
115
Activity Objective
115
Visual Objective
115
ii
Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT) v6.0
2008 Cisco Systems, Inc.
Required Resources
115
Command List
116
Job Aids
116
Task 1: Creating a Line Group and Adding Members
116
Task 2: Creating a Hunt List and Adding Line Groups
118
Task 3: Creating a Hunt Pilot Number and Associating It with a Hunt List
119
Task 4: Testing Call Distribution
119
Task 5: Configuring Final Forwarding for Busy and No-Answer Conditions
120
Lab 5-1: Implementing Media Resources
122
Activity Objective
122
Visual Objective
122
Required Resources
123
Command List
123
Job Aids
123
Task 1: Add a Software Conference Media Resource in Cisco Unified Communications Manager
123
Task 2: Add a Hardware Conference Media Resource
125
Task 3: Configure Meet-Me Conferences in Cisco Unified Communications Manager
129
Task 4: Manage MOH Audio Files
129
Task 5: Configure Multicast MOH
131
Task 6: Implement Media Resources Access Control
134
Lab 5-2: Configuring Cisco Unified Communications Manager User Features
138
Activity Objective
138
Visual Objective
138
Required Resources
138
Command List
139
Job Aids
139
Task 1: Configuring Call Park
139
Task 2: Configuring Call Pickup
140
Task 3: Configuring Do Not Disturb
141
Task 4: Configuring the Intercom Feature
142
Task 5: Configuring Cisco Call Back
143
Task 6: Configuring Barge with Built-In Conference Bridge
144
Task 7: Configuring Privacy
146
Task 8: Customize End User Web Pages
147
Lab 5-3: Configuring Presence-Enabled Speed Dials and Lists
150
Activity Objective
150
Visual Objective
150
Required Resources
150
Command List
151
Job Aids
151
Task 1: Configure Presence-Enabled Speed Dials
151
Task 2: Implement Presence Policies
152
153
Lab 5-4: Integrating Cisco Unified Communications Manager to Voice-Mail Systems
155
Activity Objective
155
Visual Objective
155
Required Resources
155
Job Aids
156
Task 1: Configure Cisco Unified Communications Manager for Voice-Mail Integration
156
Task 2: Configure Cisco Unified Communications Manager Phones to Send Calls to Voice Mail
160
Task 3: Configure Cisco Unity for Integration with Cisco Unified Communications Manager 161
Task 4: Configure Cisco Unity Subscribers and Voice-Mail Boxes
163
Lab 5-5: Enabling Cisco Unified Video Advantage
165
Activity Objective
165
Visual Objective
165
Required Resources
165
Command List
166
Job Aids
166
iii
Task 1: Enabling Video Capabilities

167
Task 2: Installing Cisco Unified Video Advantage
167
Task 3: Checking the Cisco Unified Video Advantage Connections and Video Signal Quality 168
Task 4: Configuring the Maximum Bandwidth for a Video Call
169
Answer Key
171
Lab 1-1 Answer Key: Cisco Unified Communications Manager Installation and Upgrade
Discovery
171
Lab 2-1 Answer Key: Exploring Cisco Unified Communications Manager Administration Options
173
Lab 2-2 Answer Key: Configuring Cisco Unified Communications Manager Initial Settings
179
Lab 2-3 Answer Key: Managing User Accounts in Cisco Unified Communications Manager 183
Lab 3-1 Answer Key: Configuring Voice VLANs
183
Lab 3-2 Answer Key: Implementing IP Phones
183
Lab 3-3 Answer Key: Hardening IP Phones
184
Lab 4-1 Answer Key: Implementing MGCP Gateways
184
Lab 4-2 Answer Key: Configuring Cisco Unified Communications Manager Call Routing
Components
184
Lab 4-3 Answer Key: Implementing Digit Manipulation
185
Lab 4-4 Answer Key: Implementing Calling Privileges in Cisco Unified Communications Manager
186
Lab 4-5 Answer Key: Implementing Call Coverage in Cisco Unified Communications Manager
186
Lab 5-1 Answer Key: Implementing Media Resources
186
Lab 5-2 Answer Key: Configuring Cisco Unified Communications Manager User Features
188
Lab 5-3 Answer Key: Configuring Presence-enabled Speed Dials and Lists
188
Lab 5-4 Answer Key: Integrating Cisco Unified Communications Manager to Voice Mail Systems
188
Lab 5-5 Answer Key: Enabling Cisco Unified Video Advantage
188
iv
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 1-1: Cisco Unified Communications Manager Installation and Upgrade Discovery
Lab 2-1: Exploring Cisco Unified Communications Manager Administration Options
Lab 2-2: Configuring Cisco Unified Communications Manager Initial Settings
Lab 2-3: Managing User Accounts in Cisco Unified Communications Manager
Lab 4-2: Configuring Cisco Unified Communications Manager Call Routing Components
Lab 4-4: Implementing Calling Privileges in Cisco Unified Communications Manager
Lab 4-5: Implementing Call Coverage in Cisco Unified Communications Manager
Lab 5-2: Configuring Cisco Unified Communications Manager User Features
Lab 5-3: Configuring Presence-Enabled Speed Dials and Lists
Lab 5-4: Integrating Cisco Unified Communications Manager to Voice-Mail Systems
Answer Key
Lab 1-1: Cisco Unified Communications Manager

Installation and Upgrade Discovery
Complete this lab activity to practice what you learned in the related module.
Activity Objective
In this activity, you will install a Cisco Unified Communications Manager Release 6.0 cluster
with two servers. After completing this activity, you will be able to meet these objectives:
Install a Cisco Unified Communications Manager publisher
Install a Cisco Unified Communications Manager subscriber
Visual Objective
The figure illustrates what you will accomplish in this activity.
Lab 1-1: Cisco Unified Communications

Manager Installation and Upgrade Discovery
Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
Install Cisco Unified

Communications
Manager on
subscriber server.
DHCP
10.x.2.0/24
PC-x
HQ-x .101
DHCP
10.x.3.0/24
.101
.101
.2
10.x.1.0/24
.1
.4
Install Cisco Unified

Communications
Manager on
publisher server.
CUCM2-x
.102
HQ2-x
CUCM1-x
UNITY-x
2008 Cisco Systems, Inc. All rights reserved.
CIPT1 v6.07
Required Resources
These are the resources and equipment that are required to complete this activity:
Cisco Unified Communications Manager Release 6.0 publisher
PC
Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0
Lab Devices and Their Roles

Device
Device Role in the Activity
CUCM1-x
Cisco Unified Communications Manager Release 6.0

publisher
CUCM2-x

subscriber
PC-x
PC with Internet Explorer browser
Use the credentials in the table to log in to the lab devices that require authentication.
Credentials for CUCM1-x and CUCM2-x Application Access
Device
Username / Password
Access
Cisco Unified Communications

Manager Administration GUI
CCMAdministrator /
appuserpass
https://10.x.1.1/ccmadmin

Manager Console Access
admin / adminpass
ssh:10.x.1.1
Job Aids
These job aids are available to help you complete the lab activity.
The addressing of lab devices uses the IP allocation scheme shown in the table.
IP Allocation Scheme
Parameter
Value
Voice server network
10.x.1.0/24
Data network
10.x.3.0/24
Default gateways
HQ-x: Node address .101 (for all networks)
CUCM1-x
10.x.1.1/24
CUCM2-x
10.x.1.2/24
PC-x
10.x.3.1/24
Task 1: Install Cisco Unified Communications Manager

Publisher
In this task, you will install a Cisco Unified Communications Manager publisher on a new
server.
Lab Guide
Activity Procedure
Complete these steps:
Install the Cisco Unified Communications Manager Publisher
Step 1
Access your Cisco Unified Communications Manager publisher server at the
console.
Step 2
Start the installation and perform the media check.
Step 3
When the media check is complete, and the result is pass, click OK and continue the
installation by selecting the Cisco Unified Communications Manager product as
shown in the following window:
Step 4
Confirm that you want to start the install with the version available in your DVD
drive to proceed with the installation.
Step 5
Click Proceed to start the Platform Installation Wizard.
Lab Guide
Step 6
Note
Click No in the Apply Patch window.

In a real environment, you may need this option, if you want to install new service releases
that are not included in the version stored on the DVD.
Step 7
Note
Step 8
In the next window you will be asked if you want to import windows data. Click No.
This option is relevant if you are performing an upgrade from Cisco Unified Communications
Manager Release 4.x to Cisco Unified Communications Manager Release 6.0.
In the Basic Install window, confirm that you want to install the software from
DVD, and that this type of installation does not use any imported data.
Lab Guide
Step 9
Select your time zone (for example, Pacific Time US & Canada) in the Timezone
Configuration window, and click OK to continue.
Step 10
In the Auto Negotiation Configuration window, click Yes if you want to enable
automatic negotiation of Ethernet NIC speed and duplex, depending on the
configuration on the switch port where your server is connected.
Step 11
Click No in the DHCP Configuration window. You will use a static IP address for
the Cisco Unified Communications Manager publisher.
Step 12
In the Static Network Configuration window, enter the parameters as shown, where
the pod number in this example is 1.
Lab Guide
10
Step 13
In the DNS Client Configuration window, click No.
Step 14
In the Administrator Login Configuration window enter the administrator ID admin

and password adminpass.
Step 15
In the Certificate Information window, enter the company information as shown.
Step 16
In the First Node Configuration window, confirm that this is the first node in the
cluster and click Yes:
Lab Guide
11
Step 17
Note
12
In the Network Time Protocol Client Configuration window, click No to continue

the installation without using an NTP server.
In a real environment, Cisco System strongly recommends using an external NTP server.
Only in that way can you ensure that the time on Cisco Unified Communications Manager is
accurate, which simplifies log analysis and troubleshooting.
Step 18
In the Hardware Clock Configuration window, enter the correct date and time. Click
OK.
Step 19
In the Database Access Security Configuration window, enter the security password
dbsecpass. Click OK.
Lab Guide
13
14
Step 20
Click No in the SMTP Host Configuration window.
Step 21
In the Application User Configuration window, enter the application user username
(CCMAdministrator) and password (appuserpass). Click OK.
Step 22
In the Platform Configuration Confirmation window, click OK to continue with

Cisco Unified Communications Manager installation.
Step 23
The platform installation starts. Wait until the install is complete before proceeding
to the next step.
Lab Guide
15
Verify the Cisco Unified Communications Manager Publisher Installation

Step 24
After the system reboots, the installation continues for about one hour (depending on
the server platform that is used). When the installation is complete, Cisco Unified
Communications Manager restarts automatically and displays the following screen:
Step 25
Log in to the Cisco Unified Communications Manager console using the credentials
from the Credentials for CUCM1-x and CUCM2-x table. Use the Cisco Unified
Communications Manager Console Access credentials (admin/adminpass).
Step 26
Ping the default gateway, using the command utils network ping 10.x.1.1.101.
Activity Verification
You have completed this task when you attain these results:
Cisco Unified Communications Manager publisher installation is complete:
After reboot, you see the message The installation of Cisco Unified
Communications Manager is completed successfully
You can log in to Cisco Unified Communications Manager console with the
credentials from the Credentials for CUCM1-x and CUCM2-x Application Access
table.
The server is up and running and reachable (ping) on the network:
You can ping the default gateway from the Cisco Unified Communications Manager
console using the command utils network ping 10.x.1.1.101.
Task 2: Install Cisco Unified Communications Manager

Subscriber
In this task, you will install a Cisco Unified Communications Manager subscriber on a new
server. Before starting subscriber installation, you must add the subscriber server on the
publisher server.
16
Activity Procedure
Add the Subscriber in the Cisco Unified Communications Manager Publisher GUI
Step 1
From PC-x, access the Cisco Unified Communications Manager Administration GUI
by browsing to https://10.x.1.1/ccmadmin.
Note
You must accept the certificate when the Microsoft Windows Explorer pops up with a
security alert, to access the Cisco Unified Communications Manager GUI.
Step 2
Use the username and password configured for Cisco Unified Communications
Manager Administration (CCMAdministrator/appuserpass) to log in.
Step 3
Navigate to System > Server to add the new subscriber on the publisher. Click the
Add New button.
Step 4
In the Server Configuration window, enter the following parameters, and click Save:
Note
Host Name/IP Address: 10.x.1.2 (where x is your pod number)
Description: Subscriber
You must configure the new server with its IP address, because DNS services are not used
in this lab.
Install the Cisco Unified Communications Manager Subscriber

Step 5
Access your Cisco Unified Communications Manager subscriber server at the
console.
Step 6
Start the installation and perform the media check. Click Yes.
Lab Guide
17
18
Step 7
When the media check is complete, and the result is pass, click OK and continue the
installation by selecting the Cisco Unified Communications Manager product as
shown in the window. Click OK.
Step 8
Confirm that you want to start the install with the version available in your DVD
drive to proceed with the installation. Click Yes.
Step 9
Click Proceed to start the Platform Installation Wizard.
Step 10
Click No in the Apply Patch window.
Lab Guide
19
Note
Step 11
Note
20
In a real environment, you may need this option if you want to install new service releases
that are not included in your DVD version.
In the next window, you will be asked if you want to import windows data. Click
No.
This option is relevant if you are performing an upgrade from Cisco Unified Communications
Manager Release 4.x to Cisco Unified Communications Manager Release 6.0.
Step 12
In the Basic Install window, confirm that you want to install the software from
DVD, and that this type of installation does not use any imported data.
Step 13
Select your time zone (for example, Pacific Time US & Canada) in the Timezone
Configuration window, and click OK to continue.
Lab Guide
21
22
Step 14
In the Auto Negotiation Configuration window, click Yes if you want to enable
automatic negotiation of Ethernet NIC speed and duplex, depending on the
configuration on the switch port where your server is connected.
Step 15
Click No in the DHCP Configuration window. You will use a static IP address for
the Cisco Unified Communications Manager subscriber.
Step 16
In the Static Network Configuration window, enter the parameters as shown, where
the pod number in this example is 1. Click OK.
Step 17
In the DNS Client Configuration window, click No.
Lab Guide
23
24
Step 18
In the Administrator Login Configuration window, enter the administrator

parameters with admin as user and adminpass as password. Click OK.
Step 19
In the Certificate Information window, enter the company information as shown.

Click OK.
Step 20
In the First Node Configuration window, click No.
Step 21
In the next window, confirm that this is not the first node, and that there is a
connection to the first node. Click OK.
Lab Guide
25
26
Step 22
In the First Node Access Configuration window, enter the parameter of the
publisher, as shown. The screenshot shows an example for pod 1. For the security
password, enter dbsecpass. Click OK.
Step 23
In the Platform Configuration Confirmation window, click OK to continue with

Cisco Unified Communications Manager installation.
Step 24
The platform installation starts. Wait until the install is complete before proceeding
to the next step.
Verify the Cisco Unified Communications Manager Subscriber Installation

Step 25
After the system reboots, the installation continues for about one hour (depending on
the server platform that is used). You may need to confirm the data that you have
entered to continue the installation.
Step 26
When the installation is complete, Cisco Unified Communications Manager restarts

automatically and displays the following screen:
Lab Guide
27
Step 27
Log in to the Cisco Unified Communications Manager console using the credentials
from the Credentials for CUCM1-x and CUCM2-x Application Access table.
Step 28
Ping the default gateway, using the command utils network ping 10.x.1.101.
Step 29
Log in from PC-x to the web administration GUI of Cisco Unified Communications
Manager by browsing to https:\\10.x.1.1\ccmadmin.
Step 30
Navigate to System > Cisco Unified CM and click Find. You should see both the
publisher and subscriber Cisco Unified Communications Managers in the result list.
Cisco Unified Communications Manager subscriber installation is complete:
After reboot, you see the message The installation of Cisco Unified
Communications Manager is completed successfully.
You can log in to Cisco Unified Communications Manager console with the
credentials from the Credentials for CUCM1-x and CUCM2-x Application Access
table.
The server is up and running and reachable (ping) on the network:
The Cisco Unified Communications Manager GUI is accessible from PC-x:
You can log in to Cisco Unified Communications Manager GUI with the credentials
from the Credentials for CUCM1-x and CUCM2-x Application Access table.
In the Cisco Unified Communications Manager GUI, you can see the Cisco Unified
Communications Manager subscriber server:
28
Ping the default gateway from the Cisco Unified Communications Manager console
using the command utils network ping 10.x.1.1.101.
Navigate to System > Cisco Unified CM and click Find. Both the publisher and
subscriber Cisco Unified Communications Managers are in the result list.
Lab 2-1: Exploring Cisco Unified

Communications Manager Administration
Options
Activity Objective
In this activity, you will explore Cisco Unified Communications Manager administration
options. After completing this activity, you will be able to meet these objectives:
Access the Cisco Unified Communications Manager Administration window
Access the Cisco Unified Serviceability window
Access the Cisco Unified OS Administration GUI window
Understand the Cisco Unified platform administration CLI via SSH
Visual Objective
Lab 2-1: Exploring Cisco Unified Communications

Manager Administration Options
Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
Web and SSH access to

Cisco Unified
Communications Manager.
DHCP
10.x.2.0/24
PC-x
HQ-x .101
DHCP
10.x.3.0/24
.101
.101
.2
10.x.1.0/24
.1
.4
Explore Cisco Unified

Communications
Manager
administration options.
CUCM2-x
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.08
Required Resources
Cisco Unified Communications Manager Release 6.0 publisher
Lab Guide
29
PC

Device
CUCM1-x

publisher
PC-x
Credentials for CUCM1-x Application Access
Device
Username / Password
Access

CCMAdministrator /
appuserpass

Manager Serviceability GUI
CCMAdministrator /
appuserpass
https://10.x.1.1/ccmservice

Manager OS Administration GUI
admin / adminpass
https://10.x.1.1/cmplatform
Disaster Recovery System GUI
admin / adminpass
https://10.x.1.1/drf
Job Aids
Parameter
Value
10.x.1.0/24
Data network
10.x.3.0/24
Default gateways
CUCM1-x
10.x.1.1/24
CUCM2-x
10.x.1.2/24
PC-x
10.x.3.1/24
Task 1: Access the Cisco Unified Communications Manager

Administration Window
In this task, you will verify that you can log in to Cisco Unified Communications Manager
Administration after the successful installation in the previous lab.
30
Activity Procedure
Open Microsoft Windows Explorer on PC-x and browse to the following URL:
Step 1
https:\\10.x.1.1\ccmadmin
Step 2
Log in with the credentials from the Credentials for CUCM1-x Application
Access table in the Required Resources section.
Step 3
After login, you see the following window, which shows the Cisco Unified
Communications Manager system version:
Step 4
Browse through the menus and answer these questions:
Q1)
In which menu item can you find Class of Control Partition and Calling Search
Space?
Q2)
In which menu item can you find the Enterprise Parameters option?
Q3)
In which menu item can you find registered IP phones?
Q4)
In which menu item can you add end users?
Lab Guide
31
Q5)
In which menu item can you configure the Music on Hold Audio Source?
Step 5
In the upper right corner of the web page, at the Navigation drop-down list, select
each of the remaining administration pages and log in to each of them:
Cisco Unified Serviceability
Cisco Unified OS Administration
Disaster Recovery System
Note
Step 6
You will realize that you have to use different usernames and passwords when accessing
Cisco Unified OS Administration and the Disaster Recovery System. Refer to the
Credentials for CUCM1-x Application Access table when you are not sure which username
and password to use for which application.
Use the Navigation drop-down list to log in again to Cisco Unified Communications
Manager Administration.
You can log in successfully to Cisco Unified Communications Manager GUI by browsing
to https:\\10.x.1.1\ccmadmin.
You can answer the questions in the task by navigating through the different menu items in
Cisco Unified Communications Manager GUI.
You can log in to the different administration pages by using the Navigation drop-down list
in the upper right corner of the GUI web page.

In this task, you will explore the Cisco Unified Serviceability window.
Activity Procedure
32
Step 1
Log in to the Cisco Unified Communications Manager Release 6.0 Serviceability

Administration GUI on CUCM1-x. Use the login information from the Credentials
for CUCM1-x Application Access table in the Required Resources section.
Step 2
Navigate to Tools > Service Activation and select the publisher server CUCM1-x
and then click Go. In the Service Activation window, you can see the services that
can be activated and deactivated.
Answer these questions:
Step 3
Q6)
Navigate to the Tools menu item. Which tools are available in this menu?
Q7)
Navigate to Tools > Control Center - Network Services, select the CUCM1-x server
and then click Go. Check if the Performance and Monitoring services are running.
Which services are activated in the Performance and Monitoring box?
Q8)
How long are the backup and restore services up? Check the Up Time value.
You can navigate within the Cisco Unified Communications Manager Serviceability pages
and check the network services status in Tools > Control Center - Network Services.

In this task, you will explore the Cisco Unified OS Administration web GUI.
Activity Procedure
Step 1
Log in to the Cisco Unified Communications Manager Administration GUI on

CUCM1-x. Use the login information from the Credentials for CUCM1-x
Application Access table in the Required Resources section.
Lab Guide
33
Step 2
Q1)
Answers these questions:

Navigate to Show > Cluster menu, write down the following information:
Hostname:
IP Address:
Type of Node:
Q2)
Navigate to Show > Hardware menu, write down the following information:
Platform Type:
Processor Speed:
CPU Type:
Memory:
OS Version:
Q3)
Navigate to Show > Network menu, write down the following information:
DHCP:
IP Address:
IP Mask:
Gateway:
34
Q4)
Navigate to Show > Software menu, write down the following information:
Active Version:
Q5)
Navigate to Services > Ping menu, start a ping to your gateway IP address 10.x.1.101.
Did you get an answer from your gateway?
Q6)
Where could you create a Remote Access Account in case you need remote support
from a Cisco TAC Engineer?
You can navigate within the Platform Administration pages to check platform parameters
and find:
Server information in the Show > Cluster menu.
Hardware information in the Show > Hardware menu.
Network information in the Show > Network menu.
Software information in the Show > Software menu.
Tools for troubleshooting Cisco Unified Communications Manager in the Services

menu.

In this task, you will learn to use the Cisco Unified Communications Manager Release 6.0
Platform Administration CLI access.
Activity Procedure
Step 1
Start an SSH client (for example, PuTTY) at PC-x and connect to your Cisco
Unified Communications Manager publisher via SSH using the login information
from the Credentials for CUCM1-x Application Access table in the Required
Resources section.
Step 2
When you are logged in successfully, answers these questions:
Q1)
Enter ? on CLI. What commands are listed?
Lab Guide
35
Q2)
Use the question mark again, by entering show ?. Find the command that displays the
network configuration of interface ethernet0? Write down the IP address of the default
gateway:
Q3)
What commands should you enter to see the active and inactive versions of Cisco
Unified Communications Manager?
Q4)
Which release of Cisco Unified Communications Manager is active?
You successfully logged into the Cisco Unified Communications Manager CLI:
You are able to use the various commands of the CLI:
36
By using an SSH client, you can log in to the Cisco Unified Communications
Manager CLI.
By using the question mark (?), you can see the various commands available on the
CLI interface.
Lab 2-2: Configuring Cisco Unified

Communications Manager Initial Settings
Activity Objective
In this activity, you will configure Cisco Unified Communications Manager Release 6.0 initial
settings to activate services and use the Cisco Unified Communications Manager IP address
rather than its hostname. After completing this activity, you will be able to meet these
objectives:
Upload a license file
Change the hostname of Cisco Unified Communications Manager Release 6.0 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

Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
DHCP
10.x.2.0/24
PC-x
HQ-x .101
DHCP
10.x.3.0/24
.101
.101
.2
10.x.1.0/24
.1
.4
Configure initial
settings and enable
DHCP services.
CUCM2-x
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.09
Lab Guide
37
Required Resources
Cisco Unified Communications Manager Release 6.0 cluster
PC running Windows Explorer
IP phones

Device
CUCM1-x

publisher
PC-x
Device
Username / Password
Access

CCMAdministrator /
appuserpass

Manager Serviceability GUI
CCMAdministrator /
appuserpass
https://10.x.1.1/ccmservice
Job Aids
Parameter
Value
10.x.1.0/24
Data network
10.x.3.0/24
Default gateways
CUCM1-x
10.x.1.1/24
CUCM2-x
10.x.1.2/24
PC-x
10.x.3.1/24

In this task, you will upload the license file to allow two nodes (publisher and subscriber) to be
used for call processing.
38
Activity Procedure
Step 1
Log in from PC-x to the web administration GUI of Cisco Unified Communications
Manager by browsing to https:\\10.x.1.1\ccmadmin.
Step 2
Navigate to System > Licensing > License File Upload and click the Upload
License File button. A new window pops up.
Step 3
Click the Browse button and search for the .lic file on the desktop of PC-x. Select
the file and click Open.
Note
If you do not know where to find the license file, ask your instructor for help.
Step 4
Click Upload to upload the license file in Cisco Unified Communications Manager.
Step 5
Click Continue in the next window, and wait until the License File Information box
appears. The license upload is completed.
The license file is uploaded to the Cisco Unified Communications Manager publisher:
You have uploaded the file in System > Licensing > License File Upload by clicking
the Upload License File button and selecting the correct .lic file from your local
directory.
You can see the License File Information box in the License File Upload window
after uploading the license file.
When navigating to System > Licensing > License Unit Report, the uploaded
licenses are included in the report.

In this task, you will eliminate the need for DNS by changing from DNS names to IP addresses.
Activity Procedure
Step 1
From PC-x, access Cisco Unified Communications Manager Administration.
Step 2
Go to System > Server and click Find to list all servers of your cluster.
Step 3
Click CUCM1-x and change the Host Name/IP Address field from CUCM1-x to
10.x.1.1.
Step 4
Add a description for your server. Enter Publisher in the Description field.
Step 5
Click Save.
Lab Guide
39
Note
The Subscriber has already been configured with its IP address during the installation
procedure,because installation fails if the subscriber is configured by name and DNS is not
used.
Step 6
Under System > Enterprise Parameters, check if the phone URLs still include
hostnames (CUCM1-x).
Step 7
Change all of the phone URLs to the appropriate IP address and click Save.
An IP address is used for the server name:
Go to System > Server and click Find to list all servers of your cluster.
Both the Publisher and the Subscriber should be listed with their IP address in the
Host Name/IP Address column, and with a Description.
No IP addresses are used in phone URLs:
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).

In this task, you will activate the minimum services that are required by Cisco Unified
Communications Manager to serve Cisco IP phones.
Activity Procedure
Configure Cisco Unified Communications Manager Servers
Step 1
From PC-x, access Cisco Unified Communications Manager Administration GUI.
40
Step 2
Go to System > Cisco Unified CM and click Find.
Step 3
Click on the CM_CUCM1-1 name to enter the Cisco Unified CM Configuration

window.
Step 4
Change the automatically generated Cisco Unified Communications Manager Name

to CUCM1-x (where x is your pod number).
Step 5
In the Description field, enter Publisher.
Step 6
Click Save.
Step 7
Go back through the Related Links menu to Back To Find/List and repeat the last
three steps for the subscriber CM_10.1.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 Communications Manager Serviceability GUI.
Step 9
Go to Tools > Service Activation.
Step 10
At the Select Server page, select 10.x.1.1 and then click Go.
Step 11
From the list of services, check Cisco CallManager, the Cisco TFTP, and Cisco
DHCP Monitor Service.
Note
You will need the Cisco DHCP Monitor Service to perform the next task in this lab.
Step 12
Click Save to activate these services. A pop-up window appears that 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
Completed.
Step 13
Using the related links or Tools > Control Center Feature Services, go to the
control center for feature services.
Step 14
Verify that the Cisco Communications Manager, the Cisco TFTP, and the Cisco
DHCP Monitor Services are started and activated.
Step 15
Repeat the above steps to activate the Cisco CallManager service (only) on the
subscriber.
Step 16
Verify that the Cisco CallManager service is running on the subscriber.
Verify that the new names are configured:
In the result list you should see both Cisco Unified Communications Managers with
the new configured names:
CUCM1-x
CUCM2-x
Verify that all required services are started:
In the Cisco Unified Serviceability GUI, go to Tools > Control Center Feature
Services.
Make sure that the Cisco CallManager, Cisco TFTP, and Cisco DHCP Monitor
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.
Lab Guide
41
Task 4: 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 by DHCP.
Activity Procedure
Step 1
In the Cisco Unified Communications Manager Administration GUI, navigate to

System > DHCP > DHCP Server and click the Add New button.
Step 2
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
Verify the entered parameters and click Save.
Step 4
Navigate to System > DHCP > DHCP Subnet and click Add New.
Step 5
In the DHCP Subnet Configuration window, select the newly created DHCP server
and enter the following parameters:
Subnet IP Address: 10.x.2.0
Primary Start IP Address: 10.x.2.11
Primary End IP Address: 10.x.2.19
Primary Router IP Address: 10.1.2.101
Subnet Mask: 255.255.255.0
Note
Step 6
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 have to be set again at the
DHCP subnet configuration.
Verify the entered parameters and then click Save.
42
The DHCP server is configured.
The DHCP subnet is configured.
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 5: 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 CDR and CMR service parameters.
Activity Procedure
Configure Enterprise Parameters
Step 1
Navigate to System > Enterprise Parameters.
Step 2
Activate the Enable Dependency Records parameter by setting the value to True, in
the CCMAdmin Parameters pane.
Step 3
Click OK in the pop-up window, and click Save.
Note
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 can then reconfigure those records,
so that they are associated with a different record.
Configure Service Parameters

Step 4
Navigate to System > Service Parameters and select the publisher server and 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 call detail records (CDRs) are
generated. Valid values specify True (CDRs are generated) or False (CDRs are not
generated).
Step 6
Set the CDR Log Calls with Zero Duration Flag to True in the System parameters.
Step 7
Set the CMR parameter Call Diagnostics Enabled value to Enabled Only When
CDR Enabled Flag is True in the Clusterwide Parameters (Device - General).
Note
The Call Diagnostics Enabled parameter determines whether call management records
(CMRs), also called diagnostic records, are generated. Generating CMRs without
corresponding CDRs can cause uncontrolled disk space consumption. Cisco recommends
that you 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.
Lab Guide
43
Step 8
Save the changes.
Step 9
Repeat Steps 5 and 6 for the subscriber server and save the changes.
Note
There is no need to repeat Step 7 for the subscriber server because the parameter changed
in Step 7 is a clusterwide parameter and is automatically applied to all servers.
The Dependency Records parameter is enabled:
44
In the 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 select the publisher server and the Cisco
CallManager service from the drop-down 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 above steps at the subscriber.
Lab 2-3: Managing User Accounts in Cisco

Unified Communications Manager
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 using the administration GUI
Manage user accounts using BAT
Configure Cisco Unified Communications Manager to use LDAP for user provisioning
Configure Cisco Unified Communications Manager to use LDAP for user authentication
Visual Objective
Lab 2-3: Managing User Accounts in

Cisco Unified Communications Manager
Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
DHCP
Configure and
manage user
account, locally.
10.x.2.0/24
PC-x
HQ-x .101
DHCP
10.x.3.0/24
.101
.101
.2
10.x.1.0/24
.1
.4
Manage user accounts

through LDAP,
synchronization, and
authorization.
CUCM2-x
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.010
Required Resources
Publisher running Cisco Unified Communications Manager Release 6.0
Lab Guide
45
LDAP directory server
PC running Windows Explorer

Device
CUCM1-x
PC-x
Device
Username / Password
Access

CCMAdministrator /
appuserpass
Job Aids
Parameter
Value
10.x.1.0/24
Data network
10.x.3.0/24
Default gateways
CUCM1-x
10.x.1.1/24
CUCM2-x
10.x.1.2/24
PC-x
DHCP assigned (10.x.3.0/24)
Task 1: Managing User Accounts Using the Administration GUI

In this task, you will create two end-user accounts for two different administrators. One
administrator should have full access; the other should have read access only.
Activity Procedure
Add new user through the administration GUI
In the Cisco Unified Communications Manager web GUI, configure a user as follows:
Step 1
46
From PC-x, access Cisco Unified Communications Manager Administration.
Step 2
Go to User Management > End User and click Add New.
Step 3
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.
Step 4
Step 5
User ID:
Password: password
PIN:
Last name: Phone1
First name: User1
User1
54321
Click Add New again and add a second user with these attributes.
User ID:
Password: password
PIN:
Last name: Phone2
First name: User2
User2
12345
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, gets CCM Super User access rights assigned. Go to the End
User Configuration window by clicking the User ID in the Find and List Users list.
Step 7
Click Add to User Group in the Permissions Information box on the bottom of the
page.
Step 8
In the pop-up window, click Find.
Step 9
Select the Standard CCM Super Users parameter from the resulting list, and click
Add Selected. The selected parameter is visible in the Groups box.
Step 10
In the End User Configuration window, click Save. The status changes to Update
Successful. Go back to Find and List Users list.
Step 11
The second user, User2, gets only Standard CCM Read Only access rights assigned.
Go to the Permissions Information box in the End User Configuration window and
click Add to User Group.
Step 12
In the pop-up window, click Find.
Step 13
Select the Standard CCM Read Only parameter from the resulting list, and click
Add Selected. The selected parameter is visible in the Groups box.
Step 14
Click Save.
Lab Guide
47
48
Step 15
On the top of the page, in the right corner, click the Logout link to log out the
CCMAdministrator account.
Step 16
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.
Step 17
Click the Logout link to log out User1.
Step 18
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).
Step 19
Log in as CCMAdministrator again and navigate to the End User menus. Press Find
and verify that two users are configured and that you can see the information offered
on the Find page.
Step 20
Click User1 and change the password to Cisco and the PIN to 12345.
The first end user is assigned to the standard group Standard CCM Super Users:
In the User Management > End User window, enter the End User Configuration
window and go to the Permissions Information box and check if the Standard CCM
Super Users is assigned to the user.
The second end user is assigned to the standard group Standard CCM Read Only:
In the User Management > End User window, enter the End User Configuration
window and go to the Permissions Information box and check if the Standard CCM
Read Only is assigned to the user.
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 being logged in
with the first end user name (User1).
Navigate to User Management > End User and select User1. In the User
Configuration window, change the password and PIN.
Task 2: Managing User Accounts Using BAT

In this task, you will use BAT to add users and you will configure user templates to assign
rights to users.
Activity Procedure
Activate the Bulk Provisioning Service
The Bulk Provisioning Service must be activated to work with Bulk Administration tools.
Step 1
In the Cisco Unified Communications Manager Serviceability window, navigate to

Tools > Service Activation.
Step 2
In the Service drop-down box, choose the publisher server 10.x.1.1.
Lab Guide
49
Step 3
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.
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 the
Bulk Administration tools.
Step 4
Log in to Cisco Unified Communications Manager Administration and navigate to

Bulk Administration > Upload / Download Files and click Find.
Step 5
Click the checkbox for the bat.xlt file and click Download Selected.
Step 6
Download the BAT spreadsheet to C:\ and open the BAT.xlt file. If prompted, click
Enable Macros to use the spreadsheet capabilities.
Step 7
Click the Users tab at the bottom of the spreadsheet.
Step 8
Complete all mandatory fields in each row, providing the following information:
Step 9
First Name: User3
Last Name: Phone3
UserID: User3
Password: cisco
PIN: 12345
Provide the following information for a second user:
First Name: User4
Last Name: Phone4
UserID: User4
Password: cisco
PIN: 12345
Step 10
Click Export to BAT Format to transfer the data from the BAT Excel spreadsheet
into a CSV-formatted data file.
Step 11
Click OK at the popup window. The system saves the file to C:\XLSDataFiles\.
The filename is: Users-<timestamp>.txt
Note
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 does not
get converted to the CSV format.
Add a new user template in Cisco Unified Communications Manager

User templates are used to define common features for end users.
50
Step 12
Navigate to Bulk Administration > Users > User Template and click Add New.
Step 13
In the User Template Configuration window, enter the following parameters, and
then click Save:
User Template Name: CIPT_Users
Check the check box Default Password to User ID
User Locale: English, United States
User Group: Standard CCM End Users
Insert new users in Cisco Unified Communications Manager Through Bulk Administration
The newly created .csv file will be imported in Cisco Unified Communications Manager
through the Bulk Administration.
Step 14
Go to Bulk Administration > Upload/Download Files.
Step 15
Click Add New.
Step 16
In the File text box, click Browse and locate the file in C:\XLSDataFiles\ Users<timestamp>.txt.
Step 17
In the Select the Target drop-down box, choose Users.
Step 18
In the Select Transaction Type drop-down box, choose Insert Users.
Step 19
Click Save. The status displays that the upload is successful.
Step 20
Navigate to Bulk Administration > Users > Insert Users.
Step 21
In the File Name field, enter the CSV data file that you created for this bulk
transaction (Users-<timestamp>.txt).
Step 22
Choose the user template that you created (CIPT_Users) from the User Template
Name drop-down box.
Step 23
In the Job Information area, enter as Job description CIPT1 and click the Run
Immediately radio button.
Step 24
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.
Step 25
Use the Job Scheduler to see the status of your job, in Bulk Administration > Job
Scheduler.
Verify added user in Cisco Unified Communications Manager

Step 26
Navigate to User Management > End User and click Find.
Step 27
The two newly created users, User3 and User4, should appear in the user list.
Step 28
Browse to https://10.1.1.1/ccmuser and log in with the users User3 and User4 using
the defined password cisco.
Lab Guide
51
The two new users, User3 and User4, appear in the user list:
Navigate to User > End User and click the Find button.

Use LDAP for User Provisioning
In this task, you will configure Cisco Unified Communications Manager to synchronize user
accounts with an LDAP directory.
Activity Procedure
Configure the Active Directory server
For LDAP synchronization, you will need to configure the Active Directory server as follows:
Step 1
Open a remote desktop connection to the Active Directory server (UNITY-x).
Step 2
On the Active Directory Server, navigate to Start > Programs > Administrative
Tools > Active Directory Users and Computers. Right-click Users, navigate to
New > User and configure a new user with the following properties:
User login name: CCMDirMgr
Last name: CUCM-LDAP-Access
Password: cisco
Password never expires
Do not create an Exchange mailbox
Step 3
Add the CCMDirMgr user to the administrator group: Right-click the user
CCMDirMgr and select Properties. Select the tab Member of and click Add.
Step 4
Select the Administrators group and click Add, then click OK.
Note
52
This account will be used by Cisco Unified Communications Manager to access the LDAP
directory during synchronization.
Step 5
On the Active Directory server, navigate to Start > Programs > Administrative
Tools > Active Directory Users and Computers. Right-click lab.com and select
New > Organizational Unit.
Step 6
Enter EndUsers for the name of the organizational unit and click OK.
Note
Step 7
Cisco Unified Communications Manager will refer to this organizational unit as a search
base. Therefore all users created within this organizational unit will get replicated to Cisco
Unified Communications Manager.
Right-click the newly created organizational unit EndUsers, navigate to New >
User and configure a new user with the following properties:
User login name: User5
Last name: Phone5
Password: cisco
Step 8
Repeat the previous step by adding another user with a login name User6 and a last
name Phone6.
Configure LDAP synchronization in Cisco Unified Communications Manager

To configure LDAP synchronization follow these steps:
Step 9
In Cisco Unified Communications Manager Serviceability window, navigate to

Tools > Service Activation and select the Cisco Unified Communications Manager
10.x.1.1 and click Go.
Step 10
Activate the Cisco DirSync service in the category Directory Services.
Step 11
Navigate to LDAP > LDAP System. Check the box Enable Synchronizing from
LDAP Server. The server LDAP type is Microsoft Active Directory and the LDAP
attribute for the user id is sAMAccountName.
Step 12
Click Save.
Step 13
Navigate to LDAP > LDAP Directory. Configure the LDAP directory name, by
clicking the Add New button.
Step 14
Enter the following parameters:
LDAP Configuration Name: MS-AD
LDAP Manager Distinguished Name: CCMDirMgr@lab.com
LDAP Password: cisco
LDAP User Search Base: ou=EndUsers, dc=lab, dc=com
Step 15
Activate the check box Perform Sync Just Once.
Step 16
Verify user attribute mappings: Middle Name should be middleName, Phone

Number should be telephoneNumber, and Mail ID should be mail.
Step 17
Enter the IP address of the LDAP server 10.x.1.4 and the port 389.
Step 18
Click Save.
Step 19
After the new LDAP Directory information is saved, click Perform Full Sync Now.
Lab Guide
53
Step 20
Navigate to User Management > End User and click Find. You will see six users.
Check the LDAP Sync Status for the users. Two are active (User5 and User6) and
four are inactive (User1 to User4).
Step 21
Try to log in to the user web pages as User3. This should not work anymore.
Step 22
Verify that you cannot add or delete end users in Cisco Unified Communications
Step 23
In the End User Configuration window, change the password for the User5 and
User6 users to cisco123 and the PIN to 12345.
Step 24
Click Save.
Note
Step 25
This update will work because the PIN is always locally configured and the local password is
used as long as LDAP authentication is not enabled.
On the Active Directory server, add two more users in the EndUsers organizational
unit by repeating the steps performed earlier. The users should have the following
properties:
User login names: User1 and User2
Last name: Phone1 and Phone2
Password: cisco
Step 26
In Cisco Unified Communications Manager Administration, navigate to LDAP >

LDAP Directory and perform a full synchronization.
Step 27
Verify that the two users, User1 and User2, are active in the LDAP Sync Status field
in the Find and List Users window of Cisco Unified Communications Manager.
Four LDAP directory users were imported into Cisco Unified Communications Manager.
The other two users (User3 and User4) are flagged as inactive.
Note
54
By default, inactive users are removed after 24 hours.
Users can only be added or deleted at the Active Directory server and are imported into
Cisco Unified Communications Manager user database.

LDAP Authentication
Configure Cisco Unified Communications Manager to authenticate users against an LDAP
directory.
Activity Procedure
Step 1
To configure LDAP Authentication, in Cisco Unified Communications Manager

Administration, navigate to LDAP > LDAP Authentication.
Step 2
Click Enable LDAP Authentication and enter the following parameters:
LDAP Manager Distinguished Name: CCMDirMgr@lab.com
LDAP Password: cisco
LDAP User Search Base: dc=cisco, dc=com.
Step 3
Enter the IP address of the LDAP server, 10.x.1.4, and the port number, 389.
Step 4
Click Save.
Step 5
Navigate to User Management > End User and try changing the password for an
end user, which should not be possible.
Step 6
The Password field is gone. Change the password on the Active Directory server for
User2 by right-clicking the user and clicking Reset Password.
Step 7
A new window pops up; use it to set the password to microsoft.
Step 8
Log in to the Cisco Unified Communications Manager Administration web pages

(https:\\10.x.1.1\ccmadmin) as User2 with password cisco. This does not work
anymore. Try logging in using password microsoft. This time the login should be
successful.
Step 9
In Active Directory, change the password of User2 back to cisco.
Step 10
Verify that User2 now has to use password cisco when logging into the Cisco
Unified Communications Manager Administration web pages.
Step 11
Try logging in to the user web pages with User5 or User6 and password cisco. This
does not work. The problem, however, is not an LDAP authentication failure but the
fact that the two newly created users are not yet members of any groups.
Step 12
Add User5 and User6 to the Standard CCM End Users group. Now they should be
able to access the user web pages.
Lab Guide
55
Note
User1 and User2 were configured earlier to be members of Administrator groups (one of a
group with full access and one of a group with read-only privileges). Although these two
users were flagged Inactive after the first synchronization, their local group membership was
recovered after the users had been added to Active Directory. This works while the users
are inactive (24 hours, by default). Once they are deleted from the Cisco Unified
Communications Manager database and added via Active Directory afterwards, all their
local settings (including group memberships) must be reconfigured.
End users are authenticated using the LDAP directory.
The password for end users can only be changed at the Active Directory server.
Note
56
The activity verification has already been described in the lab exercise.

Activity Objective
In this activity, you will configure a Cisco IOS LAN switch to provide PoE to Cisco IP phones.
You will also assign different VLANs to the PC (data VLAN) and to the Cisco IP Phones
(voice VLAN). After completing this activity, you will be able to meet this objective:
Configure Cisco IOS switches to provide Power over Ethernet to IP phones
Configure access VLANs in Cisco IOS switches
Configure voice VLANs in Cisco IOS switches
Visual Objective
Phone1-x
Phone2-x
Phone3-x
Configure PoE on switch

ports to provide IP phones
with power.
PoE
VLAN Voice
VLAN
Data
Configure voice and

data VLAN on
switch ports.
CIPT1 v6.011
Required Resources
Cisco IP phones
PC attached to a Cisco IP phone
Cisco IOS LAN switch
Lab Guide
57
Command List
The tables describe the commands that are used in this activity.
Cisco IOS Catalyst Series Switch Commands
Command
Description
enable
Enables you to enter privileged EXEC mode or any other

security level that is set by a system administrator.
interface fastethernet
Begins interface configuration for the Cisco Catalyst switch.
power inline auto
Enables powered-device detection. If enough power is available,

automatically allocates power to the PoE port after device
detection.
show power inline
Displays the PoE status for the specified PoE port or for all PoE
ports.
show running-config
Displays the running configuration on the switch.
spanning-tree portfast
Causes a port to enter the spanning-tree forwarding state

immediately and bypass the listening and learning states.
switchport access vlan

data_VLAN_ID
Configures the interface as a static access port with the access

VLAN ID; the range is 1 to 4094.
switchport mode access
Configures the switchport to be an access (nontrunking) port.
switchport mode trunk
Sets the port to trunk unconditionally. The port is a trunking

VLAN Layer 2 interface. The port sends and receives
encapsulated (tagged) frames that identify the VLAN of
origination. A trunk is a point-to-point link between two switches
or between a switch and a router.
switchport trunk
allowed vlan remove 14094
Removes the defined list of VLANs from those currently set

instead of replacing the list.
switchport trunk
allowed vlan vlan_id
Sets the list of allowed VLANs that can receive and send traffic
on this interface in tagged format when in trunking mode.
switchport trunk
encapsulation dot1q
Sets the encapsulation format on the trunk port to IEEE 802.1Q.

With this format, the switch supports simultaneous tagged and
untagged traffic on a port.
switchport trunk native

vlan vlan_id
Sets the native VLAN for sending and receiving untagged traffic
when the interface is in IEEE 802.1Q trunking mode. The range
is 1 to 4094.
switchport voice vlan

voice_vlan_ID
Configures the Cisco IP phone to transmit voice traffic in 802.1Q

frames, tagged with the voice VLAN ID and a Layer 2 CoS value
(the default is 5). Valid VLAN IDs are from 1 to 4094. The switch
puts the 802.1Q voice traffic into the voice VLAN.
Job Aids
This job aid is available to help you complete the lab activity.
VLAN Assignment (x is the pod number)
58
HQ Voice VLAN
HQ Data VLAN
x02
x03
Lab Guide
59
Task 1: Discovering the Cisco Catalyst IOS Switch

Configuration
In this task, you will analyze which configuration is already on the switch, and you will learn
which commands that you need to set up in a voice environment.
Activity Procedure
Configuring and verifying inline power on Cisco Catalyst IOS switches
In these configuration steps, you will configure inline power on the respective ports.
Step 1
Ask your instructor which interfaces are assigned to your pod. Write them down in
the following table:
Port Assignment on LAN Switch

Phone1-x
Phone3-x
Phone3-x
Step 2
Connect to the Cisco Catalyst switch using Telnet (IP address: 10.x.1.202) and enter
configuration mode. For the login password, use cisco. The enable secret is also
cisco.
Step 3
Use the command show power inline to determine if inline power is enabled on the
ports of your pod.
Note
Step 4
Note
Only one port per pod should have PoE enabled. This is the port that is connected to
Phone1-x to which PC-x is connected.
Configure the Cisco Catalyst switch to provide power to the other phones. Use the
following command in the interface configuration mode on the ports of your pod to
enable inline power: hostname (config-if)# power inline auto
By default, inline power is enabled on all ports of Cisco Catalyst switches. For this lab, the
inline power feature has been manually turned off on two ports per pod to allow for a better
understanding of inline power configuration.
Step 5
Verify that all phones are powered.
Step 6
Verify the admin and operational state of the configured ports with the command
show power inline.
Discovering the Cisco Catalyst IOS switch settings

Before configuring data and voice VLANs on the switch ports in the next task, you will analyze
the current configuration.
60
Step 7
Enter the command show running-config and look for the configuration of the
interfaces of your phones (refer to the table at Step 1 for interface assignments).
Step 8
On the first port of your pod, you should see that an access VLAN has been
configured:
interface FastEthernet___
description Phone1-x 7960 with PC ATTACHED
switchport access vlan x03
Note
Step 9
The power inline auto command is on, by default, so it is not displayed when viewing the
configuration.
The other ports of your pod should be configured with default settings.
description Phone2-x 7961
!
description Phone3-x 7961
Step 10
Use the command show interface FastEthernet___ switchport to view all

configuration settings of the interfaces.
Step 11
Use the command show vlan to see the configured VLANs and their port
assignment.
The admin state in the show power inline output is auto and the operational state is on.
Note
The verification steps have already been performed during the lab activity.
The IP phones connected to the switch are all powered.
One port per pod is configured as access VLAN (VLAN ID is x03 the HQ Data VLAN).
Task 2: Configuring Data and Voice VLANs

In this task, you will enable access and voice VLAN access on Cisco IOS Catalyst switch ports.
Lab Guide
61
Activity Procedure
Step 1
Refer to the VLAN Assignment table in the Job Aids section to obtain the Cisco
Catalyst switch VLAN number that applies to the IP phone in your pod.
Record the respective VLAN numbers in the space that follows:
VLAN number of phones Phone1-x to Phone3-x:
VLAN number of PC PC-x:
Step 2
Note
Step 3
Connect to the Cisco Catalyst switch in your pod and enter configuration mode.
Your instructor has already configured the data and voice VLAN. This command is for
reference only:
vlan <VLAN number>
name <VLAN name>
Configure the port of Phone1-x with dual VLAN support using the following
commands:
interface Fastethernet___
switchport voice vlan <HQ Voice VLAN number>
exit
Note
Step 4
Remember that the data VLAN (access VLAN x03) has already been configured, as you
discovered in the previous task, so you do not need to configure it.
Configure the port of Phone2-x as a trunk with a voice VLAN, using the following
commands:
switchport trunk encapsulation dot1q
switchport mode trunk
switchport voice vlan <HQ Voice VLAN number>
switchport trunk native vlan <HQ Data VLAN number>
switchport trunk allowed vlan <HQ Voice VLAN number
exit
62
This configuration option is not recommended by Cisco. This option is only used in this lab
to contrast the different available configuration options.
Note
The switchport trunk VLAN command is highly recommended when configuring the port as a
trunk in order to block VLANs other than the voice and data VLAN from the port. The native
VLAN (data VLAN in this case) is always permitted and does not need to be specified in the
switchport trunk allowed vlan command.
Step 5
Configure the port of Phone3-x for an access VLAN only (because no PC is attached
to this phone) and allow the phone to use 802.1p, using the following commands:
interface fastethernet___
switchport access vlan <HQ Voice VLAN number>
switchport voice vlan dot1p
exit
Step 6
Save the switch configuration with copy running-config startup-config.
Verify that the IP phones obtain the correct voice VLAN numbers. Use these Cisco IP
phone model-specific sequences to display the VLAN information:
First, erase the phone configuration to ensure that you are not watching existing, old
configuration on the Cisco IP phone. On all three phones, click Settings, enter **#
to unlock the phone, and then press the more softkey until you see the Erase
softkey. Press the Erase softkey. The phone will reset.
After the phone is reset, it should obtain VLAN information. Verify the VLAN ID in
the following way:
At Phone1-x (7960), click Settings and then enter 3 to view the Network
Configuration menu. Enter 19 to see the Operational VLAN ID. The VLAN
should be x03.
At Phone2-x (7961), click Settings and then enter 2 to view the Network
Configuration menu. Enter 20 to see the Operational VLAN ID. The VLAN
should be x03.
At Phone3-x (7961) press the Settings button and then enter 2 to view the
Network Configuration menu. Enter 20 to see the Operational VLAN ID. The
VLAN should be 0 because 802.1p is used at Phone3-x. The phone sends
Ethernet frames with an 802.1p tag when the VLAN ID is 0; the switch puts
these frames into the configured access VLAN (x03, which is the VLAN ID of
the Phones VLAN).
Lab Guide
63
The Cisco IP phones should obtain IP addresses for the IP network of the phones network
(10.x.2.0/24) via DHCP.
64
As configured in Lab Activity 2-2, the IP phones should get an IP address from the
DHCP server (the Cisco Unified Communications Manager publisher) for the subnet
10.x.2.0/24. Verify this by checking the IP address, mask, default gateway, TFTP
server assigned to the phone, and the IP address of the DHCP server that made the
assignment using the network configuration menu of the IP phones again.

Activity Objective
In this activity, you will add IP phones to Cisco Unified Communications Manager manually,
using BAT, and using auto-registration. 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
auto-register telephones
Add IP phones to the Cisco Unified Communications Manager database using autoregistration
Use 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

Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
DHCP
10.x.2.0/24
PC-x
HQ-x .101
DHCP
10.x.3.0/24
.101
.101
.2
10.x.1.0/24
.1
.4
Add IP phones in Cisco

Unified Communications
Manager:
Using auto registration
Using BAT
Using GUI (manually)
CUCM2-x
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.012
Lab Guide
65
Required Resources
Cisco Unified Communications Manager cluster
Cisco IP phones
Third-party SIP phone
Job Aids
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)
CUCM1-x(10.x.1.1)
10.x.2.0
10.x.2.11
10.x.2.20
10.x.2.101
255.255.255.0
10.x.1.1
Cisco Unified Communications Manager Configuration

Cisco Unified CM Name
IP Address
Function
AutoRegistration
Directory
Number Range
CUCM1-x
10.x.1.1
Publisher
20012002
Task 1: Configuring 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.
Activity Procedure
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.
66
Step 1
Navigate to System > Cisco Unified CM Group and click Find.
Step 2
Choose Default from the list displayed.
Step 3
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.
Lab Guide
67
Step 4
Use the Up arrow and Down arrow 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, if this is the default order after adding the
subscriber.
Step 5
Click Save. You might be notified about the reset of devices. Click OK if a pop-up
window appears.
Step 6
Click Add New or Copy and repeat the above procedure to create a second group
called SubPub which has the two servers listed in reverse order (CUCM2-x before
CUCM1-x).
Step 7
Verify that both groups are shown in the Find and List Cisco Unified CM Groups
page.
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; 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
Navigate to System > Device Pool and click Find.
Step 9
Click Default in the list shown.
Step 10
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
Click Copy.
Step 12
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.
68
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 Using Auto-Registration

In this task, you will configure Cisco Unified Communications Manager to automatically add
new phones using auto-registration.
Activity Procedure
Cisco Unified Communications Manager Configuration
Step 1
In order to watch the registration process per phone, unplug the Ethernet cable from
Phone2-x and Phone3-x. Keep Phone1-x (the phone to which PC-x is connected)
plugged in.
Step 2
Step 3
In the list shown, select publisher server CUCM1-x.
Step 4
Enter 2001 for the starting directory number and 2002 for the ending 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.
Step 5
Click Save.
Registering IP Phones by Auto-Registration

Step 6
Reset your IP phone Phone1-x (Cisco IP Phone 7960).
Step 7
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.
Step 8
On the registered IP phone, press the Settings button, and then enter 3 on your
keypad to view the Network Configuration of the IP phone. Press 21 to view the
Cisco Unified Communications Manager settings.
The IP address 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 IP address of the backup (secondary) Cisco Unified
Communications Manager is displayed next, with the word Standby to the right.
Step 9
Plug the Ethernet cable of Phone2-x back into the phone.
Step 10
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 Managers and their status.
Step 11
Plug the Ethernet cable of Phone3-x back into the phone.
Step 12
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 auto-register
Lab Guide
69
because the auto-registration 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
auto-registered.
Step 14
Change the descriptions of the two registered phones to Phone1-x and Phone2-x. If
Phone1-x (7960 does not have directory number 2001 assigned, change the directory
number to 2001); if Phone2-x (7961 does not have directory number 2002 assigned,
change the directory number to 2002).
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 clicking Find, the two newly registered IP
phones should be found in the list as described in the activity procedure.
The third IP phone attempts to register, but fails with a message registration rejected.
This is because auto-registration 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 telephones remain configured through auto-registration.
Activity Procedure
70
Step 1
In Cisco Unified Communications Manager Administration, navigate to Device >

Phone and click Add New.
Step 2
On the new page shown, from the Phone Type drop-down menu, choose the actual
type of the Phone3-x you use (for example, Cisco 7961). Click Next.
Step 3
On the new page shown, confirm that the SCCP device protocol is selected and click
Next.
Step 4
Obtain the MAC address from your Phone3-x. On the Phone3-x, click Settings, then
select 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:
Step 5
In the Phone Configuration window, enter the Phone3-x parameters:
MAC Address: see Step 4
Description: Phone3-x
Device Pool: SubPub
Phone Button Template: Standard 7961 SCCP
Device Security Profile: Cisco 7961 Standard SCCP Non-Secure Profile
Step 6
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.
Step 7
On the new page, click the Line [1] Add a new DN link to continue to configure
line 1 extension. Enter 2003 in the Directory Number field.
Step 8
Click Save.
Step 9
Use the Related Links to get back to the device configuration level. Then reset the IP
phone.
Step 10
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.
Step 11
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).
Step 12
Use Cisco Unified Communications Manager 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 as the primary
Cisco Unified Communications Manager (CUCM2-x) is not running the Cisco
CallManager service.
Step 13
Start the Cisco CallManager service again on the subscriber.
You have completed this activity when you attain this result:
Phone3-x registers with directory number 3001.
Phone3-x should have the subscriber as its primary Cisco Unified Communications
Manager and the publisher as its secondary Cisco Unified Communications Manager.
Task 4: Prepare the Cisco Unified Communications Manager

BAT for Adding Cisco IP Phones
In this task, you will prepare the Cisco Unified Communications Manager to add IP phones to
Cisco Unified Communications Manager using BAT.
Lab Guide
71
Activity Procedure
Activate the Cisco Bulk Provisioning Service on the Publisher
Step 1
In Cisco Unified Communications Manager Serviceability, make sure that the Cisco
Bulk Provisioning service is activated on the publisher.
Create an IP Phone Template for Use with BAT
Step 2
In Cisco Unified Communications Manager Administration, navigate to Bulk
Administration > Phones > Phone Template and click Add New.
Step 3
Select Cisco 7961 for Phone Type and click Next.
Step 4
Leave SCCP as device protocol and click Next.
Step 5
Create the new phone template with these parameters:
Template Name: BAT-7961
Description: 7961 template
Device Pool: SubPub
Phone Button Template: Standard 7961 SCCP
Device Security Profile: Cisco 7961 Standard SCCP Non-Secure Profile
Leave all other settings at their default values and click Save.
Step 6
Click the Line[1] link in the left column, then enter line1 for Line Template Name,
and click Save.
Step 7
Highlight the BAT-7961 in the Associated Devices pane and click Edit Device or
use the related links to get back to the device configuration level.
Step 8
Click the Line[2] link in the left column, then 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.
72
Step 10
Check the check box next to the bat.xlt file and click Download Selected.
Step 11
In the new dialog window, click Save, and then navigate to the C:\ directory on your
local PC.
Step 12
Change the filename in the File Name field to bat7960.xlt and click Save. Wait until
the file is downloaded to your local PC.
Step 13
Open the file on your local PC using MS Excel.
Step 14
On the Phones spreadsheet tab, click the Phones radio button, then click Create File
Format.
Step 15
On the new dialog window, highlight the Directory Number in the Line Fields
pane, and then click the right arrow button to move it to the Selected Line Fields
pane.
Step 16
Click Create, and then click Yes on the pop-up window to overwrite the existing
file.
Step 17
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.
Step 18
Check the check box next to the Dummy MAC Address field.
Step 19
On the Phones spreadsheet, enter five new IP phones with the parameters that
follow, and leave the MAC Address column empty.
Description
Directory Number 1
Directory Number 2
IPPhone6
2006
3006
IPPhone7
2007
3007
IPPhone8
2008
3008
IPPhone9
2009
3009
IPPhone10
2010
3010
Step 20
Scroll right and click the Export to BAT Format button.
Step 21
Save the new file with the suggested filename to the suggest folder. You should be
notified that the file was successfully exported. Click OK.
Step 22
Exit MS 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 and, on the new dialog window, navigate to the C:\XlsDataFiles\
directory, highlight the previously stored file, and then click Open. This will
populate the File field on the File Upload Configuration page.
Step 25
Choose Phones from the Select Transaction Type drop-down menu.
Step 26
Choose Insert Phones Specific Details from the Select Transaction Type dropdown menu and click Save.
Step 27
Choose Bulk Administration > Phones > Validate phones.
Step 28
From the File Name drop-down menu, choose the previously uploaded CSV file.
Step 29
From the Phone Template Name drop-down menu, choose the BAT-7961 template
created earlier.
Step 30
Click Submit.
Step 31
Choose Bulk Administration > Job Scheduler and click Find.
Lab Guide
73
Step 32
In the job list shown, click the Job Id link that has Validate Specific Phones in the
Description column.
Step 33
The job results should display the validation status without errors.
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.
Note
This verification task was part of the lab activity
Task 5: Insert IP Phones into the Cisco Unified

Communications Manager Database Using BAT
In this task, you will complete the last step in the Cisco Unified Communications Manager
BAT process by inserting the previously validated IP phones into the Cisco Unified
Communications Manager database.
Activity Procedure
Step 1
Go to Bulk Administration > Phones > Insert Phones.
Step 2
Select the previously uploaded CSV file from the File Name drop-down menu.
Step 3
Select BAT-7961 from the Phone Template Name drop-down menu.
Step 4
Check the check box next to Create Dummy MAC Address.
Step 5
Click the Run Immediately radio button.
Step 6
Click Submit.
Step 7
Go to Bulk Administration > Job Scheduler and click Find.
Step 8
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.
Step 9
Click the phone insertion Job Id link and make sure that the job has completed
successfully. You can also review the log file.
The phones insertion job has completed with success.
Note
74
This verification step is part of the lab activity.
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 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, delete the Cisco Unified Communications Manager telephones that
were added by using Cisco Unified Communications Manager BAT, by following these steps:
Step 1
Go to Device > Phone and click Find.
Step 2
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.
Step 3
Make sure that the only IP phones that remain are the three active IP phones (those
starting with SEP).

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
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
Click User5 and verify its configuration.
Step 3
In Cisco Unified Communications Manager Administration, go to Device > Phone

and click Add New.
Step 4
For the Phone Type, choose Third-party SIP Device (Basic) from the drop-down
menu. Click Next.
Step 5
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. Because third-party SIP phones
do not register by MAC address, the value is not relevant.
Description: SIP-Phone
Device Pool: Default
Phone Button Template: Third-party SIP Device (Basic)
SIP Phone Security Profile: Third-party SIP Device Basic Standard SIP
Non-Secure Profile
Lab Guide
75
Step 6
SIP Profile: Standard SIP Profile
Digest User: User5
On the new page, click the Line [1] Add a new DN link to continue to configure
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 into the phone display and select 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.
Step 10
Wait until the third-party SIP phone registers with Cisco Unified Communications
Manager publisher, and then place test calls to other IP phones in your group.
Step 11
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.
Step 12
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
On PC-x, the third-party SIP softphone is registered with 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 Phone page. However, it cannot be reset from Cisco Unified Communications
Manager Administration. You must manually reboot the phone from the phone itself.
Task 7: Enable Digest Authentication for a Third-Party SIP

Softphone
In this task, you will configure digest authentication to be used for the third-party SIP
softphone.
76
Activity Procedure
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
Close and reopen the X-Lite application in order to reset the SIP softphone.
Step 3
Place a call from the SIP softphone. The call should succeed, although you did not
set a digest password at Cisco Unified Communications Manager.
Note
This shows that a digest password provided by the phone is ignored as long as Cisco
Unified Communications Manager is not configured to use digest authentication for the thirdparty SIP phone.
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
Click the Copy button located to the right of the text, Third-Party SIP Device Basic
Standard SIP Non-Secure Profile.
Step 6
Change the name of the profile to Third-Party SIP (Basic) with Digest
Authentication. Enter the same text for the description.
Step 7
Activate the Enable Digest Authentication check box. Then click Save.
Step 8
Go to the phone configuration page of the SIP Phone (go to Device > Phone).
Step 9
Change the Device Security Profile to Third-Party SIP (Basic) with Digest
Authentication, click Save, and reset the phone.
Step 10
Place a call from the SIP softphone. The call should fail because Cisco Unified
Communications Manager now verifies the digest authentication password.
Note
So far you only set the digest authentication password 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.
Set a Digest Authentication Password at the End User

Step 11
Set the digest authentication password at User5 to digestpass (by going to User
Management > End User). In Cisco Unified Communications Manager, the term
for digest password is Digest Credentials.
Step 12
At PC-x, close the third-party SIP phone and reopen it in order to enable the phone
to register again. The phone should now be able to register again.
Lab Guide
77
Step 13
Place a call from the SIP softphone. The call should succeed.
Note
Cisco Unified Communications Manager is configured to use digest authentication for the
third-party SIP phone and now the digest authentication password configured at the phone
and at the corresponding end user in Cisco Unified Communications Manager are identical.
78
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.

Activity Objective
In this activity, you will harden IP phones by disabling web access and gratuitous ARP, and
blocking access to the voice VLAN. After completing this activity, you will be able to meet
these objectives:
Discover IP phone default behavior, use the IP phone Settings button to obtain network
configuration information, access the IP phone over the web, and access the network
through the PC port
From Cisco Unified Communications Manager Administration, disable the phone PC port,
Settings button, web access, GARP, and PC access to the voice VLAN
Verify that the IP phone web service is not reachable and that no packets of the voice
VLAN are seen at the PC
Visual Objective

Phone1-x
Phone2-x
DHCP
1.
Phone3-x
DHCP
2.
3.
DHCP
Disable settings
access.
Disable GARP.
Disable PC port.
10.x.2.0/24
1.
2.
Restrict
settings
access.
Disable
GARP.
1.
PC-x
HQ-x .101
DHCP
10.x.3.0/24
.101
2.
No web access to IP
phones.
No access to voice
VLAN.
.101
.2
10.x.1.0/24
.1
.4
Configure IP phone
hardening features.
CUCM2-x
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.013
Required Resources
Lab Guide
79
PC
IP phones
The lab devices shown in the Visual Objectives figure are detailed in the table.
Command List
There are no commands used in this activity.
Job Aids
Directory Numbers
Device
Directory Number
Phone1-x
2001
Phone2-x
2002
Phone3-x
2003
Parameter
Value
10.x.1.0/24
Data network
10.x.3.0/24
Default gateways
CUCM1-x
10.x.1.1/24
PC-x
Task 1: Discovering IP Phone Default Behavior

To discover the IP phone default configuration, you will access its network parameters and
browse its web server. Then you will capture voice VLAN traffic from the PC connected to the
IP phone.
Activity Procedure
Access settings button
Discover IP phone configuration settings using the Settings menu.
Step 1
80
Start discovery of the network settings on Phone1-x by clicking Settings.
Step 2
Display the Network Configuration and get an overview of the various network and
device parameters. Find the values needed to build a network map and fill out the
table provided here.
IP Phone Network Settings

Network Settings
IP Address
IP address
DHCP server
DNS server
TFTP server
Default router
Active Cisco Unified Communications
Manager
Operational VLAN ID
Access Phone Web Server

Step 3
Discover the same information without physical access to the Phone1-x. On PC-x,
open a web browser and connect to the IP phone at the IP address discovered in the
previous step. In the browser, enter http://<IPPhoneIPAddress>. Explore the
information provided by an IP phone through its web interface.
Step 4
On PC-x, open a web browser and connect to the active Cisco Unified
Communications Manager of Phone1-x. Enter https://10.x.1.1/ccmadmin in the
address field of the browser to verify access to the network.
Sniff Voice VLAN Traffic

Use the Wireshark sniffer that is installed on PC-x, which is attached to Phone1-x, to capture a
telephone conversation.
Step 5
On PC-x, launch the Wireshark application and click Capture > Interfaces. From
the list of interfaces, click Capture at the interface that has an IP address of the data
network (10.x.3.0/24). A new window opens and displays the captured packets in a
statistical form.
Step 6
Place a call from Phone1-x to Phone2-x, have a short conversation, and hang up the
call.
Step 7
Click Stop within Wireshark to terminate the live capture.
Step 8
Search for RTP packets. If you find some RTP packets, go to the next step.
Otherwise, search for UDP packets that have their source and destination IP address
in the HQ phone network (10.x.2.0). Right-click one of these packets and choose
Decode as. Decode the packets as RTP and click OK to display the relevant UDP
packets as RTP data.
Step 9
Identify the RTP streams by clicking one of the RTP packets, then click Statistics >
RTP > Stream Analysis.
Lab Guide
81
Step 10
An RTP stream analysis window opens. Click the Save Payload button.
Step 11
Select the .au format, choose forward channels, and save the audio data as
C:\audio.au. Close the Wireshark application.
Step 12
Double-click the newly created file (C:\audio.au) from Microsoft Windows

Explorer. Microsoft Windows Media Player will play the file, and you can listen to
the captured conversation.
You have filled out the IP phone Network Settings table after clicking Settings of
Phone1-x to discover the network.
You verified the information of the IP phone Network Settings table by browsing to
http://<IPPhoneIPAddress> (use the IP address of Phone1-x).
You were able to browse to the Cisco Unified Communications Manager Administration
window at URL https://10.x.1.1/ccmadmin.
You have successfully captured a conversation and were able to see signaling messages and
RTP UDP messages in the Wireshark capture.
You have saved the captured conversation to a file and were able to play back the captured
conversion using Windows Media Player.

In this task, you will disable PC ports, web access, the Settings button, and GARP, and block
access to the voice VLAN selectively on Cisco IP phones.
Activity Procedure
Step 1
In the Cisco Unified Communications Manager Administration, go to Device >

Phone.
Step 2
Click Find to list all IP phones. Choose Phone1-x.
Step 3
Scroll down to Product Specific Configuration Layout and disable these parameters:
Step 4
82
Settings Access (set to restricted)
Gratuitous ARP
PC Voice VLAN Access
Web Access
From the Find and List Phones window, choose Phone3-x. Scroll down to Product
Specific Configuration Layout and disable these parameters:
Settings Access (set to disabled)
Gratuitous ARP
Step 5
Disable the PC Port
Web Access
Reset both IP phones to activate the new configuration.
Note
In a real-life environment, if none of the features are required, you would harden all IP
phones in your infrastructure.
Step 6
On PC-x, launch the Wireshark application. Start a new capture and make a new
call. Then terminate the call and stop capturing packets in Wireshark. In Wireshark,
search for Skinny or RTP messages. You should not find any, because the PC Voice
VLAN Access parameter was disabled.
Step 7
On Phone1-x and Phone3-x, attempt to view the network settings using the settings
button. What happens?
Step 8
Unplug PC-x from Phone1-x and attach PC-x to Phone3-x.
Step 9
On PC-x, go to Start > Run, enter cmd, and click OK.
Step 10
In the newly opened window, enter ipconfig. You should get the information that
the cable is unplugged. This information appears because the PC port of Phone3-x
has been disabled. After verifying that information, reconnect PC-x to Phone1-x.
Step 11
On PC-x, launch a web browser and connect to the web server of all phones. At
Phone1-x and Phone3-x, you should not be able to access the phone web server
anymore.
At Phone1-x and Phone3-x from the PC, the IP phone web service cannot be reached by
browsing to http://<IPPhoneIPAddress> (use the IP address of Phone1-x).
At Phone1-x from the PC, voice VLAN packets cannot be sniffed anymore by using the
Wireshark application.
Note
The activity verification was part of the lab activity.
At Phone1-x, you have limited access to settings when you click Settings at the IP phone.
At Phone3-x, you have no access to settings when you click Settings at the IP phone.
At Phone3-x, the PC port is disabled by connecting your PC to the PC port of your IP

phone, Phone3-x.
Lab Guide
83
Cleanup
In order to allow the use of the Settings button and to access the phone web servers, reenable
these two settings.
Step 1
84
At Phone1-x and Phone2-x, set settings access and access to the web server to
Enabled.

Activity Objective
In this activity, you will configure Cisco Unified Communications Manager to use a Cisco IOS
MGCP gateway to connect to the PSTN using a direct T1 PRI connection to the PSTN. After
completing this activity, you will be able to meet these objectives:
Configure an MGCP gateway using T1 PRI to connect to the PSTN in Cisco Unified
Configure a Cisco IOS gateway for MGCP and obtain MGCP configuration from Cisco
Configure a route pattern toward the MGCP gateway trunk
Visual Objective

Phone1-x
Phone2-x
Phone3-x
PSTN
DHCP
DHCP
DHCP
10.x.2.0/24
PSTN
PC-x
HQ-x .101
DHCP
10.x.3.0/24
.101
T1
.101
.2
10.x.1.0/24
Add MGCP
gateway to
Unified CM.
CUCM2-x
.1
T1
.4
Configure
MGCP
gateway.
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.014
Required Resources
These are the resources and equipment required to complete this activity:
Cisco IOS MGCP gateway (for example, Cisco 2600, 2800, 3700, and 3800 Series routers)
with T1 PRI connection to PSTN
Lab Guide
85
Preconfigured PSTN with PSTN phone

IP phones
PC
Command List
The table describes the commands that are used in this activity.
Cisco IOS MGCP Gateway Commands
Command
Description
enable
Enables you to enter privileged EXEC mode or any other

security level that is set by a system administrator
debug isdn q931
Displays information about call setup and teardown of

ISDN network connections (Layer 3) between the local
router (user side) and the network
configure terminal
Enters global configuration mode
ccm-manager config
Specifies the TFTP server from which the MGCP gateway

downloads Cisco Unified Communications Manager XML
configuration files, and enables download of the
configuration
ccm-manager config server
Configures the IP address or logical name of the TFTP

server from which the XML configuration files are
downloaded
mgcp
Enables the MGCP application on the gateway
show mgcp
Displays values for MGCP parameters
show mgcp endpoint
Displays a list of all MGCP endpoints on an MGCP

gateway
show ccm-manager hosts
Displays the registration status of the MGCP gateway on

its Cisco Unified Communications Managers
Job Aids
MGCP Gateway Information
86
Call Agent
Redundant Host
10.x.1.1
10.x.1.2
Cisco Unified Communications Manager Administration Configuration for MGCP Gateway

Parameter
Data
Domain Name
HQ-x (where x is your port number)
Description
MGCP gateway

Manager Group
Default
Module in Slot 0
NM-4VWIC-MBRD (for ISR routers)
Subunit 1
VWIC2-1MFT-E1 (depends on actual hardware used)
Port
0/0
Channel Selection Order
Top Down
Task 1: Configure an MGCP Gateway Using T1 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
Add an MGCP Gateway in Cisco Unified Communications Manager
Step 1
In Cisco Unified Communications Manager Administration, go to Device >
Gateway, and, on the new page shown, click Add New.
Step 2
Choose the gateway platform (for example, Cisco 2811) that is used for Cisco IOS
MGCP gateway HQ-x (x is your cluster number) from the Gateway Type drop-down
list and click Next.
Step 3
From the Protocol drop-down list, choose the protocol type MGCP and click Next.
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
Module in Slot 0: NM-4VWIC-MBRD
Global ISDN Switchtype: 4ESS
Lab Guide
87
Caution
These steps are platform-dependent. Check with 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 and show diag
commands to see details about the hardware 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
Click the port icon 0/0/0 (far left endpoint with the question mark).
Step 7
In the next window, from the Device Protocol drop-down list, choose Digital Access
PRI and click Next.
Step 8
In the Gateway Configuration page, select the following parameters:
Step 9
PRI Protocol Type: PRI 4ESS
Channel Selection Order: Top Down
Save your changes and reset the gateway.
The MGCP gateway appears in the list when you choose Device > Gateway and click
Find.
Task 2: Configuring a Cisco IOS Gateway for MGCP

In this task, you will enable MGCP on the Cisco IOS MGCP gateway HQ-x.
Activity Procedure
Access the MGCP IOS Gateway
Step 1
Use PuTTY in Telnet to reach your MGCP gateway HQ-x (IP address
10.1.250.101). Log in and change to enable mode. The login password and enable
secret are cisco.
Step 2
In the enable mode, enter the show running-config command. No MGCP

commands are currently configured on the gateway.
Configure the MGCP IOS Gateway to Use the Configuration Server Method
Step 3
In global configuration mode, enter the following commands:
ccm-manager config server 10.x.1.1
ccm-manager config
88
exit
copy running-config startup-config
Note
Step 4
The gateway will now pull its MGCP configuration from the Cisco Unified Communications
Manager TFTP server.
Enter the show running-config command. You should see more than the two
configured MGCP commands.
You can verify that your MGCP gateway has successfully registered to the Cisco Unified
Communications Manager by using the command show ccm-manager hosts (Status shows
Registered) and using the show mgcp endpoint command to check that the MGCPcontrolled T1 PRI endpoint channels are up.
Verify the MGCP status by using the command show mgcp. The Admin State and the
Operational State should be ACTIVE.
Verify that the MGCP gateway and the MGCP endpoints are registered at Cisco Unified
Communications Manager:
Step 1
Log in to Cisco Unified Communications Manager administration GUI.
Step 2
Navigate to Device > Gateway.
Step 3
In the Find Gateways section, select Show Endpoints and click Find.
Step 4
The status of the MGCP gateway endpoint should be Registered with 10.x.1.1; the
gateway IP address should be 10.1.1.101.
Task 3: Configuring a Route Pattern Toward the MGCP

Gateway Trunk
In this task, you will configure Cisco Unified Communications Manager to route calls starting
with a 9 to the MGCP gateway trunk interface.
Activity Procedure
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: 9.@
Description: Temporary Route Pattern to PSTN
Numbering Plan: NANP
Lab Guide
89
Gateway/Route List: S0/SU0/DS1-0@HQ-x
Called Party Transformation, Discard Digits: PreDot
Step 3
Click Save. You are notified by a pop-up window that the authorization code will
not be activated. Click OK.
Step 4
Then you are notified by another pop-up window that changes will reset the
gateway. Click OK.
From a Cisco IP phone in your pod, you can successfully reach a PSTN number (part of the
simulated PSTN). Specifically, perform these steps:
Step 1
At PC-x, start Cisco IP Communicator.
Step 2
Cisco IP Communicator should display PSTN-Phone-x in the top right corner of its
display. On top of the softkeys, it should display Cisco Unified CME. If your Cisco
IP Communicator does not display this information, ask your instructor for help.
Step 3
Place a call from one of your Cisco IP phones to a valid telephone number. Prepend
a 9 to indicate that the call should be sent to the PSTN using the MGCP gateway
HQ-x. An example for such a number is 9-1-800-555-1234.
Step 4
At the PSTN phone (Cisco IP Communicator running on PC-x), accept the call. This
call was sent through your HQ-x PSTN gateway.
Clean up
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:
90
Step 1
Go to Call Routing > Route/Hunt > Route Pattern, and click Find.
Step 2
Select the newly created route pattern 9.@ and click Delete Selected.

Communications Manager Call Routing
Components
Activity Objective
In this activity, you will configure Cisco Unified Communications Manager for PSTN calls
using multiple gateways. After completing this activity, you will be able to meet these
objectives:
Configure a second MGCP gateway for redundant PSTN access
Configure a route plan that includes a route group, route list, and route pattern that enables
calls to the PSTN
Enable Cisco Dialed Number Analyzer and use it for dial plan verification
Visual Objective
Lab 4-2: Configuring Cisco Unified CallCommunications Manager Routing Components

Phone1-x
Phone2-x
Phone3-x
PSTN
DHCP
DHCP
DHCP
10.x.2.0/24
PSTN
HQ-x .101
T1
T1
PC-x
1. Add
a second
gateway (HQ2-x) for
redundancy.
DHCP 10.x.3.0/24
.101
2. Use Cisco Dialed
.101
Number
Analyzer for
.2
10.x.1.0/24
path verification.
CUCM2-x
.1
.4
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.015
Required Resources
Lab Guide
91
IP phones
MGCP gateway
PC
Command List
Job Aids
Cisco Unified Communications Manager Administration Configuration for redundant MGCP GW
Parameter
Data
Domain Name
HQ2-x (where x is your port number)
Description
Redundant MGCP gateway

Manager Group
Default
Module in Slot 0
NM-4VWIC-MBRD (for ISR routers)
Subunit 1
VWIC2-1MFT-E1 (depends on actual hardware used)
Port
0/0
Channel Selection Order
Top Down
Task 1: Configure a Redundant MGCP Gateway for Additional

PSTN Access
In this task, you add another MGCP PSTN gateway to Cisco Unified Communications
Manager in order to provide redundant PSTN access.
Activity Procedure
Add a Redundant MGCP Gateway
Step 1
Navigate to Device > Gateway and, on the new page shown, click Add New.
92
Step 2
Choose the gateway platform, Cisco 2811, for Cisco IOS MGCP gateway HQ2-x (x
is your pod number) from the Gateway Type drop-down list and click Next.
Step 3
Select from the Protocol drop-down list the protocol type MGCP and click Next.
Step 4
Enter the following parameters in the Gateway Configuration window, then click
Save:
Domain Name: HQ2-x (where x is your pod number)
Description: HQ2-x PSTN Gateway
Module in Slot 0: NM-4VWIC-MBRD
Global ISDN Switchtype: 4ESS
Step 5
In the Configured Slots, VICs and Endpoints pane from the Subunit 0 in Slot 0,
choose the module VWIC2-1MFT-T1E1-T1. Click Save.
Step 6
Click the port icon 0/0/0 (far left endpoint with the question mark).
Step 7
In the next window, select Digital Access PRI for the Device Protocol and click
Next.
Step 8
In the Gateway Configuration page, select the following parameters:
Step 9
PRI Protocol Type: PRI 4ESS
Channel Selection Order: Top Down
Click Save, and, when the pop-up window appears, click OK.
Note
The redundant MGCP Gateway HQ2-x does not physically exist. It is only added to
demonstrate how Cisco Unified Communications Manager can be configured to use multiple
gateways.
The MGCP gateway appears in the list when you choose Device > Gateway and click
Find.
Task 2: Configuring a Route Plan Using MGCP Gateways that

Includes a Route Group, Route List, and Route Pattern
In this task, you will configure routing to the PSTN through both gateways, when one MGCP
gateway is not available.
Activity Procedure
Create a Route Group in Cisco Unified Communications Manager
Step 1
Navigate to Call Routing > Route/Hunt > Route Group and click Add New.
Step 2
Step 3
Enter the following parameters in the Route Group Information window:
Route Group Name: RG_MGCP_GWs
Distribution Algorithm: Top Down
In the Available Devices pane, add both MGCP gateways (HQ-x and HQ2-x) by
selecting the gateway endpoints and clicking Add to Route Group. Use the arrows
on the right side of the box to move the HQ2-x endpoint to the first place.
Lab Guide
93
Step 4
Click Save.
Create a Route List in Cisco Unified Communications Manager

Step 5
Navigate to Call Routing > Route/Hunt > Route List and click Add New.
Step 6
Enter the following parameters in the Route List Configuration window:
Name: RL_MGCP_GWs
Description: MGCP PSTN Gateways
Step 7
Click Save.
Step 8
In the updated route list configuration page, select the newly created route group by
clicking Add Route Group in the Route List Member Information pane.
Step 9
Click Save. Click OK in the pop-up window.
Create a Route Pattern in Cisco Unified Communications Manager

Step 10
Go to Call Routing > Route/Hunt > Route Pattern, and click Add New.
Step 11
In the Route Pattern Configuration window, enter the following parameters:
Route Pattern: 9.!#
Description: PSTN Access with #
Gateway/Route List: RL_MGCP_GWs
Called party discard digits instructions: PreDot
Step 12
Click Save. You are notified by a pop-up window that the authorization code will
not be activated. Click OK.
Step 13
Then you are notified by another pop-up window that changes will reset the
gateway. Click OK.
Step 14
Repeat the above steps to create an identical route pattern but without the # sign (9.!)
and with a description PSTN Access with Interdigit Timeout.
Note
You can use the copy icon to create a copy of the existing route pattern which you can
modify as required.
94
From a Cisco IP phone in your pod, you can successfully reach a PSTN number using the
prefix code 9 (for example, 9-323-456-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. Although the route list prefers HQ2-x,
due to its absence, the call is sent through HQ-x. Verify that the call is received at PSTNPhone-x and accept the call at the PSTN phone.
At gateway HQ-x, you can monitor call signaling activity by using the debug command
debug isdn q931.
Task 3: Enable DNA and Use It for Dial Plan Verification

In this task, you will install DNA and use it to verify correct call routing.
Activity Procedure
Activate Cisco Dialed Number Analyzer Service
Step 1
Access Cisco Unified Communications Manager Serviceability, and go to Tools >
Service Activation. Choose the publisher server 10.x.1.1 from the Server dropdown list. Click Go.
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 will display as Activated.
The service is activated and the Activation Status column displays the status as
Activated.
Access Cisco Dialed Number Analyzer

Step 4
To access DNA, go to Tools > Dial Number Analyzer in Cisco Unified
Communications Manager Serviceability.
Step 5
Note
A new pop-up window appears. If you are prompted to enter the user name, enter
CCMAdministrator as the user ID and in the Password field, enter the password
appuserpass. Click OK. You are now logged in to DNA.
You can also use the URL https://10.x.1.1/dna to access DNA. You do not have to access it
from Cisco Unified Communications Manager Serviceability.
Perform a Simple Analysis by Using the Analyzer Window

Step 6
Navigate to Analysis > Analyzer.
Step 7
Enter the calling party digits 2002 in the Calling Party field. By default, 1000
displays in this field.
Step 8
Enter the digits 911 (or any other number starting with 9), in the Dialed Digits field.
Step 9
Start the analysis, by clicking Do Analysis.
Step 10
When you click Do Analysis, DNA analyzes the dialed digits and displays the
results in a new window, the DNA Analysis Output window.
Step 11
In the DNA Analysis Output window, click Expand All. Under Call Flow, at the
end of the Route List output section, you will see the gateways listed in the order in
Lab Guide
95
which they are used to route the call. Note that HQ2-x is listed first. The call is only
sent out at HQ-x, because the first option, HQ2-x is not available.
96
In Tools > Control Center - Feature Services, the Cisco DNA 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 PSTN number (any number starting with 9).
You performed call analysis using Cisco DNA. The output shows that gateway HQ2-x is
preferred for calls to the PSTN.
Lab Guide
97

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
Used For Called Numbers On Outgoing Calls
Configure Cisco Unified Communications Manager to Extend Calling Numbers in

Outgoing Calls to Fully Qualified PSTN Numbers
Configure Cisco Unified Communications Manager to Reduce 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
Visual Objective

Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
DHCP
10.x.2.0/24
PC-xoff
Strips 51x-555
called number of
incoming calls from
DHCP
the PSTN.
Prefixes 9 to the
calling number of
incoming PSTN
calls.
PSTN
HQ-x .101
10.x.3.0/24
T1
.101
T1
.101
.2
PSTN
10.x.1.0/24
PSTN Phone
CUCM2-x
.1
.4
Uses .102
ISDN debug to
see digit manipulation
results.
Dials 51x-555-2002.
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.016
Required Resources
98
IP phones
PC
MGCP gateway
PSTN gateway
PSTN phone
Job Aids
Transformation Masks (where x is your pod number)
Cluster Name
IP Phones
External Phone Number Mask
Pod x
Phone1-x, Phone2-x, Phone3-x
51x5552XXX

Strip Access Codes Used for Called Numbers on Outgoing
Calls
In this task, you will configure access code stripping on route patterns.
Activity Procedure
Step 1
Go to Call Routing > Route/Hunt > Route Pattern and click Find.
Step 2
Click one of the two existing route patterns (9.!# or 9.!).
Step 3
Verify that in the Called Party Transformations pane, a DDI PreDot is selected.
Step 4
Repeat the above for the other route pattern.
Step 5
At gateway HQ-x, enter debug isdn q931 in enable mode.
Note
Step 6
As you access HQ-x via Telnet, do not forget to turn on terminal monitor in order to see the
debug output.
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.
At gateway HQ-x, you see that the access code was removed from the called number.
Lab Guide
99

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
Step 1
Step 2
Choose Phone1-x.
Step 3
At the Phone Configuration page, click Line [1] to get to the line configuration page
of the phone.
Step 4
Enter an External Phone Number Mask of 51x5552XXX.
Step 5
Click Save.
Step 6
Repeat the above procedure for Phone2-x, Phone3-x, and Phone4-x.
Step 7
Reset all four phones from the Find and List phone page.
Step 8
Go to Call Routing > Route/Hunt> Route Pattern and click Find.
Step 9
Enter the Route Pattern Configuration window by clicking the route pattern 9.!#.
Step 10
In the Calling Party Transformations pane, click the Use Calling Party's External
Phone Number Mask check box.
Step 11
Click Save.
Step 12
Repeat the above procedure for route pattern 9.!#.
Step 13
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 E.164
number rather than a 4-digit extension.
100
On outgoing PSTN calls, the calling number is shown as an E.164 PSTN number
(51x5552XXX). This can be verified at the PSTN phone receiving the call or by examining
debug isdn q931 output at the gateway (HQ-x).

Reduce the Called E.164 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 limit called E.164 numbers to internally used directory numbers.
Activity Procedure
Try to Place Calls from the PSTN into Your Cluster
Step 1
Try placing a call from the PSTN phone to Phone1-x by dialing 1-51x-555-2001.
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 51x5552001. Cisco Unified Communications
Manager rejects the call because no phone is configured with such a long number,
but, internally, 4-digit directory numbers are used.
Enable Calls from the PSTN into Your Cluster
Step 2
In order 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
In the Translation Pattern field, enter 51x5552XXX (where x is your pod number).
Step 4
In the Description field, enter Translation of incoming 10-digit PSTN calls.
Step 5
Make sure that the Provide Outside Dial Tone box is not checked.
Step 6
In the Called Party Transform Mask field, enter 2XXX.
Note
The X in the called party transformation mask is case-sensitive; x is not accepted.
Step 7
Click Save.
Step 8
Click Copy to create a copy of the translation pattern. This translation pattern should
translate called numbers for calls coming from the PSTN from 7-digit PSTN
numbers to the 4-digit directory number.
Step 9
Change the Translation Pattern field to 5552XXX.
Step 10
In the Description field, enter Translation of incoming 7-digit PSTN calls.
Step 11
Click Save.
Lab Guide
101
Note
In this scenario, it would be easier to set the significant digits at the HQ-x gateway to 4. This
setting will trim the called number on incoming calls to the last 4 digits. However, such a
configuration is not always possible, for instance when internal directory numbers are not in
sync with PSTN direct inward dial ranges or when variable-length numbering plans are
used.
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
In the Translation Pattern field, enter 2XXX.
Step 14
In the Description field, enter Translation for Unassigned Directory Numbers.
Step 15
Make sure that the Provide Outside Dial Tone box is not checked.
Step 16
In the Called Party Transform Mask field, enter 2002.
Step 17
Click Save.
Place calls from the PSTN phone to the IP phones in your pod:
Dial 1-51x-555-2001. Phone1-x should ring.
Dial 555-2002. Phone2-x should ring.
Dial 1-51x-555-2004. Phone4-x should ring.
Dial 555-2009. Phone2-x should ring because 2009 is an unassigned directory

number and therefore, after performing the first translation from 5552009 to 2009,
the called number matches translation pattern 2XXX, which translates the called
number to 2002.
Note
Depending on the line you use at the PSTN phone, calls are received from different calling
numbers. However, all calling numbers use PSTN format, so they do not include access
code 9 (and the 1 on 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.

Prefix an Access Code to Calling Numbers on Incoming Calls
In this task, you will configure a transformation of the calling number on incoming PSTN calls
so that received or missed calls can be called back from call lists without the need to edit the
number.
Activity Procedure
102
Step 1
Go to Call Routing > Translation Pattern and click Find.
Step 2
Click Translation Pattern 51x5552XXX to get to the translation pattern

configuration page.
Step 3
In the Calling Party Transformations pane, enter 91 in the Prefix Digits (Outgoing
Calls) field.
Step 4
Click Save.
Step 5
Repeat the above procedure for Translation Pattern 5552XXX by entering 9 in the
Prefix Digits (Outgoing Calls) field.
Place a call from the PSTN phone to one of the IP phones in your pod:
From line 2 (long-distance) of the PSTN phone, dial the long-distance number of
Phone1-x (1-51x-555-2001). You should see the call being received from
916665554444.
From line 1 (local) of the PSTN phone, dial the local number of Phone2-x (5552002). You should see the call being received from 95554444.
Lab Guide
103
Lab 4-4: Implementing Calling Privileges in Cisco

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 Forced Authorization Codes
Visual Objective
Lab 4-4: Implementing Calling Privileges in

Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
DHCP
Manager phone
requires FAC for
international calls
outside of
business hours.
PSTN
10.x.2.0/24
Lobby phone can

place calls only to
regular employees
and emergency.
PSTN
PC-x
HQ-x .101
DHCP
10.x.3.0/24
.101
CUCM2-x
T1
.101
.2
Regular employee phone

cannot place international
calls outside of business
hours.
T1
10.x.1.0/24
Configure CoS,
time-based
routing, and FAC.
.1
.4
PSTN Phone
Outside callers cannot

reach the manager phone.
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.017
Required Resources
104
IP phones
PC
PSTN gateway
PSTN phone
Job Aids
Partitions
Partition Name
Description
Assigned to Devices
Lobby-Phones
Lobby phones
2001
Phones
Employee phones and 2XXX
2002
2004
Translation patterns:
2XXX, 51x5552XXX, 5552XXX
Manager-Phones
Manager phones
2003
Partition Name
Description
Assigned to Route Patterns
PSTN-Local_LD
PSTN: Local and Long-Distance
9.[2-9]xxxxxx
9.1[2-9]xx[2-9]xxxxxx
PSTN-Intl_ToD
PSTN: International - office hours only
9.011!
9.011!#
PSTN-Intl_FAC
PSTN: International - FAC
9.011!
9.011!#
PSTN-Emergency
PSTN: Emergency
911
9.911
PSTN-Free
PSTN: Toll Free
9.1[800,866,877,888]xxxxxxx

Lab Guide
105
Calling Search Spaces

Calling Search Space
Name
Description
Contains Partitions
Lobby IP phone
(2001)
Lobby_css
CSS for Lobby Phones
Phones
Employee IP phone
(2002, 2004)
Phones_css
Devices
PSTN-Emergency
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
PSTN gateway(s)
To-Phones_css
CSS for gateways and

translation patterns
Phones
Route Pattern
Route Partition
Description
Gateway/Route List
911
PSTN-Emergency
PSTN: Emergency
RL_MGCP_GWs
9.911
PSTN-Emergency
PSTN: Emergency
RL_MGCP_GWs
9.1800xxxxxxx
PSTN-Free
PSTN: Toll Free
RL_MGCP_GWs
9.[2-9]xxxxxx
PSTN-Local_LD
PSTN: Local
RL_MGCP_GWs
9.1[2-9]xx[2-9]xxxxxx
PSTN-Local_LD
PSTN: Long Distance
RL_MGCP_GWs
9.011!
PSTN-Intl_ToD
PSTN: International,
office hours only
RL_MGCP_GWs
9.011!#
PSTN-Intl_ToD
office hours only
RL_MGCP_GWs
9.011!
PSTN-Intl_FAC
FAC required outside
office hours
RL_MGCP_GWs
9.011!#
PSTN-Intl_FAC
FAC required outside
office hours
RL_MGCP_GWs
Translation patterns:
2XXX, 51x5552XXX,
5552XXX
Route Patterns
106
Task 1: Configuring Partitions and CSSs

In this task, you will create partitions and CSSs in Cisco Unified Communications Manager
Administration.
Activity Procedure
Configuring Partitions
Step 1
Go to Call Routing > Class of Control > Partition, and click Add New.
Step 2
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.
Configuring CSSs
Step 4
Go to Call Routing > Class of Control > Calling Search Space, and click Add
New to open the Calling Search Space Configuration window.
Step 5
Using the Calling Search Spaces table (in the Job Aids section of this lab activity),
enter the first CSS name and description.
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 using the downward arrow. To remove a
partition from the list of Selected Partitions, highlight the partition and click the
upward arrow.
Note
Use the Shift key to highlight multiple contiguous entries and the Ctrl key to select multiple
noncontiguous entries.
Step 7
Click Save.
Step 8
Repeat the previous steps to create the remaining CSSs that are listed in the Calling
Search Spaces table.
Note
When you configure the Manager_css calling search space, make sure that the PSTNIntl_ToD partition is set before the PSTN-Intl_FAC partition. This will be important when
time-of-day routing is implemented and a forced authorization code has to be entered if
international calls are placed outside business hours.

Lab Guide
107
When you navigate to Call Routing > Class of Control > Partition and then click Find,
you see all partitions that you added.
When you navigate to Call Routing > Class of Control > Calling Search Space and click
Find, you see all calling search spaces that you have added.
Note
Further verification will be performed during the following tasks.
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
Assigning Partitions and Calling Search Spaces to IP Phones
Step 1
Step 2
Click the IP phone with the directory number 2001 to open the Phone Configuration
page.
Step 3
Click Line [1] - 2001 from the left page column to access the Directory Number
Configuration page.
Step 4
Choose Lobby-Phones for the Route Partition, and in the Directory Number
Settings, choose Lobby_css for the Calling Search Space.
Step 5
Click Save.
Step 6
Repeat Steps 1 to 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 calling search space configuration parameters applicable to these
remaining IP phones.
Step 7
Go to Device > Phone and click Find, then choose all four IP phones and click
Reset Selected, then click Reset again, and click Close in the pop-up window
shown.
108
The Lobby IP phone (2001) is able to call only Employee IP phones (2002 and 2004) but
cannot dial the Manager IP phone at (2003).
The Employee IP phones (2002 and 2004) are able to call all other IP phones.
The Manager IP phone (2003) is able to call the Employee phones (2002 and 2004) and the
Lobby Phone (2001).
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
Assigning Partitions and Calling Search Spaces to Translation Patterns
Step 1
Go to Call Routing > Translation Pattern and click Find.
Step 2
Click the translation pattern 2XXX to open the Translation Pattern Configuration
window.
Step 3
Choose Phones from the Partition drop-down menu.
Step 4
Choose To-Phones_css from the Calling Search Space drop-down menu.
Step 5
Click Save.
Step 6
Repeat the previous steps for the other two translation patterns.
Assigning Partitions and Calling Search Spaces to Gateways

Step 7
Choose Device > Gateway, and click Find to list all the gateways.
Step 8
At the HQ-x MGCP gateway, click the See Endpoints link in the Status column.
Note
Each endpoint of an MGCP gateway is controlled separately; therefore CSSs are applied
individually per endpoint and not at the gateway level.
Step 9
Select the Device Name (e.g. S0/SU0/DS1-0@HQ-1) to access the endpoint

configuration page.
Step 10
Scroll down the page to see the Call Routing Information Inbound Calls section
where the CSS can be configured. Set the appropriate CSS according to the job aid
table.
Step 11
Click Save and reset the MGCP endpoint.
Step 12
Repeat the previous steps for gateway HQ2-x.
The PSTN phone is able to call employee phones (555-2002 or 555-2004).

Lab Guide
109
If the PSTN dials the manager or lobby IP phone (555-2001 or 555-2003) the call is sent to
the attendant (2002).
If an unassigned directory number is dialed from the PSTN phone (for example, 555-2010),
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, longdistance, and toll-free PSTN destinations. You
will also configure route patterns to international destinations, which will be restricted in the
next task.
Activity Procedure
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
Go to Call Routing > Route/Hunt > Route Pattern and click Find.
Step 2
Select the 9.! route pattern.
Step 3
Change the route pattern to 911 and the description to PSTN Emergency.
Step 4
Set the partition to PSTN-Emergency.
Note
110
The discard digits instruction PreDot will be greyed out because it is not applicable anymore.
Step 5
Save your changes.
Step 6
Repeat the previous steps by changing the 9.!# route pattern to 9.911. Again, set the
partition to PSTN-Emergency and change the description to PSTN Emergency. Do
not forget to save your changes.
Step 7
Click the Copy button in the Route Pattern Configuration window and update the
following parameters with the values of the next route pattern shown in the Route
Patterns table of the Job Aids section.
Route Pattern: 9.1800XXXXXXX
Route Partition: PSTN-Free
Description: PSTN: Toll Free
Step 8
Make sure that the Discard Digits option in the Called Party Transformations pane is
set to PreDot. Make sure that the Use Calling Partys External Phone Number Mask
check box is activated in the Calling Party Transformations pane.
Step 9
Click Save. And on the subsequent popup windows, click OK.
Step 10
Repeat the last three steps to create the remaining route patterns as described in the
Route Patterns table in the Job Aids section.
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 only dial 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-699-18900009, emergency: 9-911 or
911, and toll free: 9-1-800-555-4444).
Note
At this stage, ignore the route pattern in partition PSTN-Intl_FAC. It is not relevant here
because it is identical to the route pattern PSTN-Intl_ToD. Also, note that partition PSTNIntl_ToD does not have a time schedule applied at this point and therefore is always active
in the CSSs that include the partition.
Task 5: 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 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
Create a Time Period
Step 1
Go to Call Routing > Class of Control > Time Period and click the Add New
button.
Step 2
Step 3
In the Time Period Configuration window, enter the following parameters:
Name: 9a-5p_Mo-Fr
Time Of Day Start: 0
Time Of Day End: 24
Repeat Every Week from Monday to Sunday
Click Save.

Lab Guide
111
Note
The requirement in this task is to permit calls during business hours, such as 9:00 a.m. to
5:00 p.m. as indicated in the name of the time period. However, in order to easily simulate a
call that is placed within business hours and a call that is placed outside business hours, the
time 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 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 placed outside business
hours. In reality, you would configure something like 0900 to 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
In the Time Schedule Configuration window, enter BusinessHours in the Name

field, and move the 9a-5p_Mo-Fr time period from the Available Time Periods
pane in the Selected Time Periods.
Step 6
Click Save.
Assign the Time Schedule to ToD Partition

Step 7
Navigate to Call Routing > Class of Control > Partition and click Find.
Step 8
Click the partition with the name PSTN-Intl_ToD.
Step 9
In the Partition Configuration window, choose the newly created time schedule
BusinessHours in the Time Schedule field.
Step 10
Click Save.
112
You have created a Time Schedule and Time Period.
Employee phones can only dial international destinations during business hours. Verify this
as follows:
Step 1
From Phone2-x or Phone4-x, dial any international number (for example, 9-011-43699-18900009). 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 permitted.
Step 2
In order to simulate a call outside business hours, go to Call Routing > Class of
Control > Time Period and click Find. Select 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.
Step 3
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 therefore denied.
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 phones
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: Implement Forced Authorization Codes

In this task, you will configure Cisco Unified Communications Manager to require a Forced
Authorization Code (FAC) to be entered at manager phones when dialing nternational
destinations outside business hours.
Activity Procedure
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
Click Save.
Step 4
Repeat the previous steps to add another FAC with name Too Low Level, code
9998 and level 4.
Step 5
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.
Step 6
In the Route Pattern Configuration window, activate the Require Forced

Authorization Code checkbox. Set the minimum required Authorization Level to 5.
Step 7
Click Save.
Step 8
Repeat the previous steps for the 9.011!# route pattern in the PSTN-Intl_FAC
partition.
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:

Lab Guide
113
Step 1
Dial an international destination (for example, 9-011-43-699-18900009) 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,
indicating that an FAC has to be entered.
Step 2
Enter FAC 9999 followed by # and the call should be permitted.
Step 3
Dial the same number again, but this time enter FAC 9998 followed by # and the
call should be denied because the authorization level configured for FAC 9998 is not
high enough for the matched route pattern.
Step 4
Dial the same number again, but this time enter an invalid FAC (for example, 9997)
followed by # and the call should be denied.
Step 5
Change the time period back to 00:00 24:00, Monday to Friday (as described in
the previous task).
Step 6
Dial the same number again. This time there will be no prompt for an FAC.
Note
114
The CSS of the manager phone has partition PSTN-Intl_ToD listed before partition PSTNIntl_FAC. If the time-of-day partition is active (that is, during business hours) a route pattern
is matched that does not require an FAC. If the call is placed outside business hours, the
partition PSTN-Intl_ToD is not active in the phones 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; not
only if the call is placed outside business hours.
Lab 4-5: Implementing Call Coverage in Cisco

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
Lab 4-5: Implementing Call Coverage in

Phone1-x
Phone2-x
Phone3-x
2ndLG
DHCP
DHCP
PSTN
DHCP
10.x.2.0/24
PSTN
PC-x
1stLG
HQ-x .101
10.x.3.0/24
Configure.2 line 10.x.1.0/24

group,
hunt list, hunt pilot, and
CUCM2-x
final
forwarding.
.1
.4
.101
.101
T1
DHCP
T1
PSTN Phone
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.018
Required Resources
IP phones
PC

Lab Guide
115
Command List
Job Aids
There are no job aids for this activity.
Task 1: Creating a Line Group and Adding 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
Create a Line Group
Step 1
Choose Call Routing > Route/Hunt > Line Group and click Add New.
Step 2
Enter 1stLG in the Line Group Name field.
Step 3
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).
Step 4
Change the RNA Reversion (RNAR) Timeout from its default value of 10 seconds
to 5 seconds.
Note
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.
Add Members to the Line Group

Step 5
Add the 2001 and 2003 directory numbers to the line group. 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.
116
Step 6
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.
Step 7
Click Save to add the new directory numbers to the line group.
Step 8
Repeat the previous steps to create a second line group named 2ndLG with member
2002/Phones.
Two line groups have been added to Cisco Unified Communications Manager with their
respective members. You can see these two line groups if you choose Call Routing >
Route/Hunt > Line Group and click Find.

Lab Guide
117
Task 2: Creating a Hunt List and Adding 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
Step 1
Go to Call Routing > Route/Hunt > Hunt List.
Step 2
Click Add New.
Step 3
In the Hunt List Name field, enter the name 1stHL and in the Description field enter
First Hunt List.
Step 4
From the drop-down list, choose Default as Cisco Unified Communications

Manager Group.
Step 5
Activate the Enable this Hunt List check box and click Save.
Step 6
Add the previously created line groups to the new hunt list. To add a line group,
click Add Line Group. The Hunt List Detail Configuration window appears.
Step 7
From the Line Group drop-down list, choose the 1stLG line group and then click
Save. Then click OK on the pop-up window. The line group name will appear in the
Hunt List Configuration window in the Selected Groups pane.
Step 8
Click the Add Line Group button again, and repeat the last steps to add the
remaining line group, 2ndLG, to the hunt list.
Note
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 needed, 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 9
Click Save on the Hunt List Configuration window. Then click OK on the pop-up
that reminds you to reset the hunt list.
Step 10
Click Reset to reset the hunt list. When the dialog window appears, click Reset and
then click Close.
118
One hunt list that contains two line groups has been added to Cisco Unified
Communications Manager. You can verify that if you choose Call Routing > Route/Hunt
> Hunt List and then click Find.
Task 3: Creating a Hunt Pilot Number and Associating 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
Step 1
Choose Call Routing > Route/Hunt > Hunt Pilot.
Step 2
Click Add New.
Step 3
Enter 2111in the Hunt Pilot number field and Hunt Pilot 1 in the Description field.
Step 4
Select partition Phones from the Route Partition drop-down list.
Step 5
Assign the hunt pilot to the 1stHL hunt list using the Hunt List field drop-down
menu.
Step 6
Click Save.
You created a hunt pilot number 2111 and assigned it to the hunt list:
Go to Call Routing > Route/Hunt > Hunt Pilot and then click Find to verify if
your hunt pilot has been correctly created.

In this task, you will test and validate the call-distribution behavior to ensure that it operates as
desired.
Activity Procedure
Step 1
Note
Step 2
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.
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

Lab Guide
119
group because Try next member, then, try next group in Hunt List is specified as
the hunt option. 2002 will ring for 5 seconds, then hunting fails.
Step 3
In order to be able to run into a busy condition on a phone line, you have 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. In detail, perform the following steps to enable a
busy condition on line 2001:
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.
Step 5
Place a call from 2003 to 2001 and keep the call open in order 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.
Step 6
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).
Calls to the hunt pilot will hunt and achieve call distribution according to the configured
hunt option and distribution algorithm.
Note
More specific verification was part of the activity procedure.
Task 5: Configuring Final Forwarding for Busy and No-Answer

Conditions
In this task, you will configure final forwarding on the hunt pilot number so that a call
forwarded to the hunt pilot that is not answered (because of no-answer or busy conditions) is
forwarded to a destination directory number (presumably, in a production network, to a
designated number in the hunt group, an auto-attendant, or voice-mail system).
Activity Procedure
Step 1
120
Choose Call Routing > Route/Hunt > Hunt Pilot, and then click Find.
Step 2
Choose 2111 to go to the Hunt Pilot Configuration window.
Step 3
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: 2003
Forward Hunt Busy CSS: Phones_css
Maximum Hunt Timer: 12 seconds
Step 4
Click Save.
Step 5
Choose Call Routing > Route/Hunt > Line Group and click Find.
Step 6
Choose 1stLG to go to the Line Group Configuration window.
Step 7
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.
Step 8
Click Save.
Step 9
Following the procedure described in the previous task, change the Busy Trigger
parameter at line 2003 to 2.
Step 10
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?
Write down your assumption and then test your hypothesis.
Step 11
Place a call from 2003 to 2001 and keep the call open in order 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.
Step 12
Hang up all calls.
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 hunts at 2003 for 5 seconds. After these 5
seconds the call gets forwarded to 2003. At Phone3-x, Forwarded For 2111 appears on the
display.
Cleanup
To prepare for future labs, follow the procedure described in the previous task to change the
Busy Trigger parameter at line 2001 back to 2.

Lab Guide
121

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
Configure Meet-Me conferences in Cisco Unified Communications Manager
Manage MOH audio files
Configure multicast MOH
Implement media resources access control
Visual Objective

Phone1-x
Phone2-x
DHCP
DHCP
Phone3-x
Use MOH and

conferences.
PSTN
DHCP
10.x.2.0/24
PSTN
PC-x
.1
.4
HQ-x .101
T1
.101
.101
T1
Configure media resources:

MOH
DHCP 10.x.3.0/24
Hardware conference bridge
Software
.2 conference
10.x.1.0/24 bridge
Implement media resource
CUCM2-x control.
access
PSTN Phone
Configure
hardware
conference
bridge.
.102
HQ2-x
CUCM1-x
UNITY-x
122
CIPT1 v6.019
Required Resources
Cisco IOS voice gateway with hardware conference capability
MGCP gateway
Audio files (.wav format)
Command List
The table describes the commands that are used in this activity.
DSPFARM IOS Commands
Command
Description
voice-card <card number>
Enters voice-card configuration mode to configure its

resources
dsp services dspfarm
Configures DSP farm services for a voice card
Sccp
Enables SCCP and its related applications (transcoding and

conferencing)
sccp local <interface>
Selects the local interface that the SCCP applications

should use to register with Cisco Unified Communications
Manager
sccp ccm <CCM ipaddress>

priority
Adds Cisco Unified Communications Manager server to the

list of available servers and sets its priority
dspfarm transcoder maximum

sessions
Specifies the maximum number of transcoding sessions to

be supported by a DSP farm
dspfarm confbridge maximum

sessions
Specifies the maximum number of concurrent conference

sessions for which DSP farm resources should be allocated
dspfarm
Enables DSP farm services
Job Aids
Task 1: Add a Software Conference Media Resource in Cisco

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.

Lab Guide
123
Activity Procedure
Activate the Cisco IP Voice Media Streaming Application Service
Step 1
In the Cisco Unified Serviceability window, go to Tools > Service Activation.
Step 2
Choose the first node from the Server drop-down menu (10.x.1.1).
Step 3
Activate the Cisco IP Voice Media Streaming App service.
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. They are automatically
generated during installation with a description of CM_(server name as entered
during installation). The name is usually CFB_2 for the first installed server, CFB_3
for the next installed server, and so on. The conference bridges are only running
when the IP Voice Media Streaming App service is activated on the appropriate
server.
Step 6
Click the conference bridge name CFB_2 (the bridge of the publisher) to enter the
Conference Bridge Configuration window.
Step 7
Change the name to SW-CFB_CUCM1-x.
Step 8
Change the Description to Software Conference Bridge CFB_CUCM1-x.
Step 9
Click Save.
You have successfully completed this task when you attain these results:
124
In Tools > Service Activation, the 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 the SWCFB_CUCM1-x registered.
Try to establish an ad-hoc conference with three participants. Specifically, perform these
steps:
Step 1
Establish a call from Phone2-x to Phone1-x.
Step 2
At Phone2-x, press the More softkey to browse through the available softkeys. Press
the Confrn softkey and dial 2003.
Step 3
At Phone3-x, accept the call.
Step 4
At Phone2-x, press the Confrn softkey.
Step 5
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 Conferee
List. Note that the creator of the conference can also remove participants from the
conference.

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
Configure a Cisco IOS Router as a Hardware Conference Media Resource
Step 1
Connect to your HQ-x router and enter enable mode.

Lab Guide
125
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
command show interface fastethernet0/0 to see the output similar to this example.
Make note of the MAC address shown on your output.
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
Step 3
You must use the MAC address of the interface where 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.
Make router DSP resources available as a hardware conference bridge and have
them registered at your Cisco Unified Communications Manager. In global
configuration mode, enter this sequence of commands:
voice-card 0
dspfarm
dsp services dspfarm
sccp local FastEthernet0/0.x01

sccp ccm 10.x.1.1 identifier 1 version 5.0.1
sccp ccm 10.x.1.2 identifier 2 version 5.0.1
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
126
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, for instance, based on the
output in Step 2, would be CFB000F34D90D00.
dspfarm profile 1 conference

codec g711ulaw
codec g711alaw
maximum sessions 2
associate application SCCP
no shutdown
exit
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
Click Add New.
Step 6
From the Conference Bridge Type drop-down menu, choose Cisco IOS Enhanced
Conference Bridge.
Step 7
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).
Tip
The name of the media resource is case sensitive!
Step 8
For the Description, enter Hardware Conference Bridge CFB_HQ-x.
Step 9
Choose Default for the Device Pool.
Step 10
Choose Non Secure Conference Bridge for the Device Security Mode.
Step 11
Click Save.
Connect to your conference bridge router HQ-x and enter the command show sccp. Verify
that the Conferencing Oper State is ACTIVE and that the TCP Link Status is
CONNECTED.
Enter the command show sccp ccm group 1. Verify that the group is associated with both
Cisco Unified Communications Managers and the dspfarm profile.

Lab Guide
127
128
Enter the command show dspfarm profile 1. 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

In this task, you will configure Cisco Unified Communications Manager to support Meet-Me
conferences.
Activity Procedure
Step 1
In Cisco Unified Communications Manager Administration, go to Call Routing >

Meet-Me Number/Pattern.
Step 2
Click Add New.
Step 3
In the Meet-Me Number Configuration window, enter the following parameters:
Step 4
Meet-Me Number Configuration: 45XX
Description: Meet-Me Range
Partition: Phones
Click Save.
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
Upload an MOH Audio File
Step 1
Resources > MOH Audio File Management.
Step 2
Click Upload File.

Lab Guide
129
Step 3
Click Browse and select a .wav file stored on your computer (for example, Windows
XP Logon Sound.wav in C:\WINDOWS\Media\). Alternatively, ask your instructor
for a Music on Hold .wav file.
Step 4
Click Upload File.
Step 5
Wait until the Status changes to Upload successful, then click Close.
Step 6
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.
Add a New MOH Audio Source

Step 7
Go to Media Resources > Music On Hold Audio Source and click Find.
Step 8
You will see one entry (MOH Audio Stream Number 1 the SampleAudioSource).
Click Add New.
Step 9
Configure a second MOH audio source with the following parameters:
Step 10
MOH Audio Stream Number: 2
MOH Audio Source File: <Name of previously uploaded file (see Step 3)>
MOH Audio Source Name: Custom MOH
Play continuously (repeat) check box: Activated
Click Save.
Configure a Phone to Use the New Audio Source

Step 11
Step 12
Enter the configuration for Phone1-x.
Step 13
Change the User Hold MOH Audio Source from <None> to 2.
Step 14
Save your changes and reset the phone.
Note
The default User and Network Hold MOH Audio Source is 1 and was applied through the
device pool. By modifying the User Hold MOH Audio Source at Phone1-x only, the default
MOH file is played, unless the user at Phone1-x puts a call on hold.
130
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:
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.
Step 2
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
Phone2-x and keep the call open.
Step 3
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.
Step 4
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.
Step 5
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.
Note
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.
Task 5: Configure Multicast MOH

In this task, you will configure Cisco Unified Communications Manager to use multicast MOH
rather than unicast MOH.
Activity Procedure
Enabling Multicast MOH on Audio Sources
Step 1
Resources > Music On Hold Audio Source and click Find.
Step 2
Enter the configuration of MOH Audio Stream Number 1 and activate the Allow
Multicasting check box. Click Save.
Step 3
Repeat the previous step for MOH Audio Stream Number 2.
Enabling 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 (this should be the MOH server running

Lab Guide
131
on the publisher; its name should be MOH_2) to enter the MOH Server
Configuration window.
Step 6
In the Multicast Audio Source Information pane, click the Enable Multicast Audio
Sources on this MOH Server check box.
Step 7
Verify that the Base Multicast IP Address is 239.1.1.1.
Step 8
Set the Increment Multicast On parameter to IP Address.
Step 9
Verify that the Max Hops parameter for Multicast Audio Source 1 is set to 2.
Step 10
Click Save and, in the popup window, click OK.
Step 11
Click Reset and, in the popup window, click Reset and then Close.
Enabling 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.x01
ip pim sparse-dense-mode
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.x02).
You have successfully completed this task when you attain this result:
When MOH is played, multicast MOH is used rather than unicast MOH. To verify your
configuration, you can watch the packets that are sent out on interface FastEthernet0/0.x03.
Perform the following steps for verification:
Step 1
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
132
ip access-group 101 out

exit
copy running-config startup-config
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.

Lab Guide
133
Step 2
Use the command show access-lists 101 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)
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
Keep your Telnet session to HQ-x open.
Step 4
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 command show access-lists 101 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.
Note
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
Multicast MOH is not used because for multicast MOH, media resource groups and media
resource group lists are required and the Use Multicast for MOH Audio check box at the
media resource group must be activated. Media resource groups and media resource group
lists are only implemented in the next task, so you will only be able to verify your multicast
MOH configuration in the activity verification of the next task.

In this task, you will assign media resources to media resource groups, assign media resource
groups to media resource group lists, and assign different media resource group lists to different
IP phones. This will allow selective media resource allocation per device (phone) and enable
the use of multicast MOH.
Activity Procedure
134
Configure Media Resource Groups

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

parameters:
Name: HW-CFB_mrg
Description: IOS Hardware Conference Bridge
Step 3
From the Available Media Resources, select the Cisco IOS hardware conference
bridge HW-CFB_HQ-x .
Step 4
Click Save.
Step 5
Click Add New and enter following parameters:
Name: SW-CFB_mrg
Description: Software Conference Bridge
Step 6
From the Available Media Resources, select the software conference bridge SWCFB_CUCM1-x.
Step 7
Click Save.
Step 8
Click Add New and enter following parameters:
Step 9
Note
Step 10
Note
Step 11
Name: Other-SW-MR_mrg
Description: Other SW Media Resources: Annunciator, MoH, MTP
From the Available Media Resources, select ANN_2, MOH_2[Multicast] and

MTP_2.
The software media resources ending with _3 are not active because the Cisco IP Voice
Media Streaming App has not been activated on the appropriate server (CUCM2-x).
Therefore, there is no need to add them into any media resource group.
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 media resource group to
use multicasting (if enabled at the MOH servers).
Click Save.
Configure Media Resource Group Lists

Step 12
Go to Media Resources > Media Resource Group Lists and click Add New.
Step 13
In the Media Resource Group List configuration window, enter HW-SW_mrgl for
the name.

Lab Guide
135
Step 14
From the Available Media Resource Groups, select all groups and make sure to
order them as follows:
HW-CFB_mrg
SW-CFB_mrg
Other-SW-MR_mrg
Note
Step 15
As the hardware conference bridge should be used before the software conference bridge,
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 media resource group list. The position of this media resource group within
the media resource group list is not relevant because this is the only media resource group
containing such types of media resources.
Click Save.
Assign the Media Resource Group Lists to Phones

Step 16
Go to System > Device Pool and click Find.
Step 17
Change the Media Resource Group List from <None> to HW-SW_mrgl.
Step 18
Click Save.
Step 19
Click Reset and reset all devices using this device pool.
Step 20
From the Related Links, select Dependency Records and click Go. You will see a
record summary indicating which device types (and their number) are using this
device pool.
Step 21
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).
136
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:
Step 1
End all active calls.
Step 2
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.
Note
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, a
Meet-Me conference is in place with Phone4-x as the only member (after Phone1-x dropped
out).
Step 3
In a Telnet session to HQ-x, use the command show dspfarm dsp active to verify
that the hardware conference bridge is used for the conference. Keep the call active
at Phone4-x.
Step 4
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.
Note
Phone3-x cannot create conferences because it does not have a media resource group list
assigned, and all media resources are put into media resource groups. However, as the
Meet-Me conference was created by another phone, a second conference is in place with
Phone3-x as the only member (after Phone1-x dropped out).
Step 5
Again, use the command show dspfarm dsp active at HQ-x to verify that the
hardware conference bridge is also used for the second conference. Keep the call
active at Phone3-x.
Step 6
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.
Step 7
At HQ-x, use the command show dspfarm dsp active again to verify that this third
conference does not use the hardware conference bridge (becausse 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).
Step 8
End all calls.
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 tone on hold is played at Phone3-x.
Note
Phone3-x cannot listen to MOH because it does not have a media resource group list
assigned and all media resources (including the MOH server) are put into media resource
groups. Therefore Phone3-x does not have access to any MOH server and tone on hold is
played instead of MOH.
When Phone2-x or Phone3-x is put on hold, it hears MOH. Use the command show accesslists 101 at HQ-x to verify that, this time, multicast MOH is used.

Lab Guide
137

Communications Manager User Features
Activity Objective
In this activity, you will configure user features such as Call Park, Call Pickup, Hold Reversion,
and Intercom, and you will customize user web pages and configure IP phone services. After
completing this activity, you will be able to meet these objectives:
Configure Call Park, Directed Call Park, Call Pickup, and Hold Reversion
Configure DND, Intercom, Cisco Call Back, Barge, and Privacy
Configure Cisco Unified Communications Manager to support user web pages
Configure IP phone services
Visual Objective

Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
User features:
DHCP
10.x.2.0/24
PC-x
HQ-x .101
DHCP
10.x.3.0/24
Intercom
Barge and Privacy
CallBack
User Web Page
Call Pickup
.101
.101
.2
10.x.1.0/24
Configure
user
features
CUCM2-x
.1
.4
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.020
Required Resources
138
Three Cisco IP phones
PC
Command List
Job Aids
Task 1: Configuring Call Park

In this task, you will configure a Call Park number and then use the Call Park feature within
your cluster.
Activity Procedure
Step 1
In Cisco Unified Communications Manager Administration, add a new partition

called Features.
Step 2
Add partition Features to the Lobby_css, Phones_css, and Manager_css calling

search spaces.
Step 3
Go to Call Routing > Call Park.
Step 4
Click Add New to open the Call Park Configuration page.
Step 5
Enter 266X for the Call Park Number/Range field. In the Description field, enter
Call Park Range.
Step 6
Select Features for the Partition.
Step 7
Choose CUCM1-x as the Cisco Unified Communications Manager to which the

Call Park range should be assigned. Click Save.
Establish a call from Phone1-x to Phone2-x. At Phone2-x, park the call by pressing the
Park softkey. The IP phone where the call was parked goes on-hook and displays a
message Call park At 266n, while the call at Phone1-x displays a connection To Park
Number: 266n. (where n is any number out of the configured call park range). Take note
of the Call Park number.
At Phone3-x, call the number where the call has been parked in order to get connected to
the parked party (Phone1-x).
Disconnect the call.

Lab Guide
139
Task 2: Configuring Call Pickup

In this task, you will configure the Call Pickup feature.
Activity Procedure
Create a New Call Pickup Group
Step 1
Navigate to Call Routing > Call Pickup Group and click Add New.
Step 2
Step 3
Configure the new Call Pickup group with following parameters:
Call Pickup Group Name: SalesGroup
Call Pickup Group Number: 2550
Description: Sales Group
Partition: Features
Call Pickup Group Notification Policy: Visual Alert
Click Save.
Create a Softkey Template that Includes the Call Pickup Softkey

Step 4
Go to Device > Device Settings > Softkey Template, and click Find.
Step 5
Copy the Standard User Softkey Template and rename it to Customized User. Enter
Customized (based on Standard User) for the description and click Save.
Step 6
At the Related Links, select Configure Softkey Layout and click Go.
Step 7
Add the Pick Up softkey to the softkey template for the on-hook call state.
Step 8
Click Save.
Assign a Call Pickup Group and Softkey Template to IP Phones

Step 9
Step 10
Enter the configuration page for Phone2-x.
Step 11
Apply the newly created softkey template to the phone and click Save.
Step 12
Enter the directory number configuration for line 1.
Step 13
Apply the newly created Call Pickup group to the line and click Save.
Step 14
Repeat the previous steps for Phone3-x.
Step 15
Step 16
Select Phone2-x and Phone3-x and click Reset Selected, followed by Reset and
Close.
140
Place a call from Phone1-x to Phone2-x. At Phone3-x, pick up the call by using the Pickup
softkey.
Task 3: Configuring Do Not Disturb

In this task, you will configure the DND feature.
Activity Procedure
Update User Softkey Template
Step 1
Go to Device > Device Settings > Softkey Template, and select the Customized
User softkey template.
Step 2
At the Related Links, select Configure Softkey Layout and click Go.
Step 3
Add the toggle Do Not Disturb softkey to the following call states:
On Hook
Off Hook
Ring in
Tip
You have to save the changes per call state.
Click Reset followed by Restart and Close in order to allow the devices using the softkey
template to learn about the changes you have made.
Note
The softkey template has already been assigned to Phone2-x and Phone3-x in the previous
task.
Configure Device-Based DND Parameters

Step 4
At the phone configuration page in Cisco Unified Communications Manager,
configure Phone2-x with the following DND setting and save your changes.
DND Incoming Call Alert: Beep Only
You can use DND at Phone2-x and Phone3-x. Specifically, perform these steps:
Step 1
At Phone2-x, press the DND softkey. The phone will display a message Do Not
Disturb Is Active.
Step 2
Place a call from Phone1-x to Phone2-x. Phone2-x will indicate the incoming call by
a beep. End the call setup attempt at Phone1-x.
Step 3
Press the DND softkey again at Phone2-x. DND will be disabled.

Lab Guide
141
Step 4
Place a call from Phone4-x to Phone3-x. When the phone starts ringing, press the
DND softkey at Phone3-x. The phone stops ringing and indicates the incoming call
only visually. Press the DND softkey again and the phone rings again to indicate the
incoming call.
Task 4: Configuring the Intercom Feature

In this task, you will configure and test the Intercom feature.
Activity Procedure
Configuring the Intercom Partition and Calling Search Space
Step 1
Go to the Intercom > Intercom Route Partition menu.
Step 2
Step 3
Click Add New. Enter the following data and click Save.
Intercom Partition Name: Intercom1
Intercom Partition Description: Intercom1 Partition
Navigate to the Intercom > Intercom Calling Search Space menu, and search for
existing CSSs. You will find a CSS named Intercom1_GEN. This CSS has been
created automatically by Cisco Unified Communications Manager. Click the
Intercom1_GEN CSS and verify that the automatically generated CSS includes the
partition that you created before.
Configuring the Intercom Directory Numbers

Step 4
Go to the Intercom > Intercom Directory Number menu and click Add New.
Enter the following data and click Save:
Directory Number: 8002 to 8003
Route Partition: Intercom1
Description: Intercom Phone2-Phone3
Alerting Name: Intercom
ASCII Alerting Name: Intercom
Calling Search Space: Intercom1_GEN
Step 5
At the Related Links, select Back to Find/List and click Go.
Step 6
Verify that two Intercom directory numbers have been created.
Update Phone Button Template for the Intercom Feature

Step 7
Navigate to Device > Device Settings > Phone Button Template and click Find.
142
Step 8
Copy the phone button template that applies to Phone2-x and Phone3-x (Standard
7961 SCCP) and set the name to Customized 7961. Click Save.
Step 9
Change button 3 to Intercom and click Save.
Apply Phone Button Template and Assign Intercom Line to the Phones
Step 10
Go to Device > Phone and enter the configuration page for Phone2-x.
Step 11
Apply the newly created phone button template and click Save.
Step 12
Click the Intercom line (button 3) to add a new Intercom.
Step 13
At the Intercom Directory Number Configuration page, enter the following settings
and click Save:
Note
Intercom Directory Number: 8002
After you leave the input field (for example, by pressing the Tab key) the intercom directory
number configuration you created earlier is automatically loaded.
Display (Internal Caller ID): Phone2
Line Text Label: Intercom to Phone3
Speed Dial: 8003
Step 14
Click Save and then reset the intercom line.
Step 15
Repeat the previous steps for Phone3-x, swapping 8002 against 8003 (and vice
versa) and Phone2 against Phone3 (and vice versa).
Phone2-x and Phone3-x can use the Intercom feature. Specifically, perform these steps:
Step 1
At Phone3-x, hit the Intercom phone button. The button will light up orange and a
one-way communication is possible from Phone3-x to Phone2-x.
Step 2
At Phone2-x, you can hear the caller (Phone3-x) and you can accept the Intercom
call by pressing the (orange) Intercom button. The button light on both phones turns
to green and a normal two-way call is established.
Step 3
End the call and establish an Intercom call from Phone2-x to Phone3-x.
Step 4
At Phone3-x, press the EndCall softkey to reject the Intercom call.
Task 5: Configuring Cisco Call Back

In this task, you will enable the Cisco CallBack softkey to allow the use of the Cisco CallBack
feature. This feature allows you to request a call-back notification after a call attempt ends in a
busy condition.
Activity Procedure
Complete these steps.
Step 1
Change the Customized User softkey template by adding the CallBack softkey to the
call states On Hook and Ring Out.

Lab Guide
143
Note
The CallBack softkey in the Ring Out state is used during a call-back request when a call is
in the ringing or busy state or when the call has been forwarded to voice mail.
Note
The CallBack softkey in the on-hook call state enables you to check the status of a call-back
request that was previously initiated or to cancel a call-back request that is no longer
desired.
Step 2
After changing the softkey template, click Reset in order to update the phones that
use the reconfigured softkey template.
You can successfully request callback notification after trying to call a busy phone.
Specifically, perform these steps:
Step 1
Establish a call between Phone1-x and Phone2-x and keep the call open.
Step 2
From Phone3-x, call Phone2-x. Do not accept the call at Phone2-x. After a few rings
press the CallBack softkey at Phone3-x. Information will be displayed that
CallBack is activated for 2002. Press the Exit softkey to leave the CallBack
information screen.
Step 3
You can verify Call Back status or cancel waiting for a Call Back at any time by
pressing the CallBack softkey. Do this now to get back to the Call Back information
screen.
Step 4
Press the Cancel softkey to cancel waiting for a Call Back.
Step 5
From Phone3-x, call Phone1-x. Again, do not accept the call but press the CallBack
softkey again at Phone3-x.
Step 6
End the call between Phone1-x and Phone2-x. You will get audible and visual
CallBack notification at Phone3-x. Press the Dial softkey to call Phone1-x.
Task 6: Configuring Barge with Built-In Conference Bridge

In this task, you will configure and use the Barge feature. Barge allows a user to be added to a
connected call that is made to or from another device on a shared line. To use Barge, you must
first configure a shared line appearance and enable Barge by setting a clusterwide Cisco
CallManager service parameter.
Activity Procedure
Create a Shared Line
Step 1
Choose Device > Phone, and click Find to show the list of available IP phones.
144
Step 2
Select Phone2-x.
Step 3
Click Line 2 Add a new DN.
Step 4
In the Directory Number field, enter 2009, and choose Phones for the Route
Partition.
Step 5
Set the CSS to Phones_css.
Step 6
Click Save. Then reset the line.
Step 7
Go to Device > Phone, and click Find to show the list of available IP phones.
Step 8
Select Phone3-x.
Step 9
Click Line 2 Add a new DN.
Step 10
In the Directory Number field, enter 2009.
Note
After leaving the Directory Number field (for example, by pressing the Tab key) the existing
configuration of that directory number is loaded. Verify that the route partition is Phones and
that the CSS is Phones_css.
Step 11
Click Save. Note that the Associated Devices list box contains two phones (Phone2x and Phone3-x).
Step 12
Reset the line.
Test the Shared Line

Step 13
Take the Phone2-x off-hook and press the Line 2 button. At Phone3-x (which shares
the line), notice that the second line also indicates the off-hook state. Hang up the
line at Phone2-x.
Step 14
Note
From Phone1-x, place a call to 2009. Phone2-x and Phone3-x will ring. Accept the
call at one phone.
The phone where the shared line is active shows a green light at the phone button. At the
inactive phone, the shared line phone button is red.
Change Service Parameters for Privacy Settings

Step 15
Choose System > Service Parameters.
Step 16
From the Server drop-down menu, choose 10.x.1.1. From the Service drop-down
menu, choose the Cisco CallManager service.
Step 17
Scroll the page down to locate the Clusterwide Parameters (Device - Phone) section.
Change the Privacy Setting to False.

Lab Guide
145
Note
Privacy is enabled by default. When Privacy is enabled, Barge is not permitted. In order to
allow configuration and testing of Barge, Privacy is disabled here. More details about
Privacy configuration are provided in the next task, in which Privacy will be configured in a
way to allow the phone user to selectively enable and disable Privacy.
Change Service Parameter to Enable Barge

Step 18
Scroll down to locate the Clusterwide Parameters (Device - Phone) section. Change
the setting of the Builtin Bridge Enable to On.
Step 19
Scroll down to locate the Clusterwide Parameters (Feature - General) section.

Ensure that the Party Entrance Tone parameter is set to True. This parameter will
enable or disable a tone on the telephone of the Barge target when another user is
barging into the call.
Step 20
Click Save. Wait until the page refreshes.
Note
The Barge softkey is included in the Standard User softkey template. Because the softkey
template that you applied to Phone2-x and Phone3-x in earlier tasks is also based on the
Standard User softkey template, it also contains the Barge softkey.
From Phone1-x, dial 2009. Phone2-x and Phone3-x will ring at line 2. Answer the call at
Phone2-x.
At Phone3-x, press the Line 2 phone button (shared line). The Barge softkey should
appear. Press the Barge softkey to join the conversation. The IP phone displays the To
Barge message.
At Phone1-x, end the call. Now Phone1-x will be connected to Phone3-x (only).
End all calls.
Task 7: Configuring Privacy

In this task, you will assign a Privacy phone button to an IP phone so that you can invoke
Privacy to prevent other users of a shared line from viewing call information or using Barge to
join the call.
Activity Procedure
146
Step 1
Go to Device > Device Settings > Phone Button Template and click Find.
Step 2
Choose the Customized 7961 phone button template.
Step 3
Change button 4 to Privacy and click Save.
Step 4
Click Reset to reset all devices using the phone button template.
IP phones with Privacy enabled indicate the Privacy feature at their displays at phone
button 4.
A user of a shared line can permit or deny other users of the shared line from viewing
connection information or barging into the call. Perform these steps to verify your
configuration:
Step 1
From Phone1-x, dial 2009. Answer the call at Phone2-x.
Step 2
Press the Privacy feature button (phone button 4) at Phone2-x several times to see
how Privacy gets enabled and disabled. When Privacy is enabled, Phone3-x does not
see the number that is connected to the shared line. When Privacy is disabled,
Phone3-x can see the number. Leave Privacy enabled and keep the call open.
Note
Privacy is enabled when a dot is shown within the circle and when the light of the phone
button is orange.
Step 3
At Phone3-x, press the phone button of the shared line (second phone button). You
will not see the Barge softkey and there is no indication that the other phone is busy
on the shared line. Dial 2004 to call Phone4-x. Enable and disable Privacy at
Phone3-x and watch how the display changes at Phone2-x.
Step 4
At Phone3-x, end the call on the shared line. At Phone2-x, disable Privacy.
Step 5
At Phone3-x, barge into the call on the shared line. Enable Privacy at Phone2-x and
note that the barged call is not removed from the conference.
Task 8: Customize End User Web Pages

In this task, you will customize the end user web page by disabling user-configurable PINs and
labels.
Activity Procedure
Associate Devices with End Users
Step 1
In Cisco Unified Communications Manager, go to User Management > End User
and click Find.
Step 2
Select User5 and click Device Association.
Step 3
At the User Device Association page, click Find to search for devices.
Step 4
Select at least one directory number of Phone1-x and Phone2-x and click Save
Selected/Changes.
Step 5
At the Related Links, select Back to User and click Go.

Lab Guide
147
Step 6
Back at the End User Configuration page, click Save.
Log In to User Web Pages

Step 7
Access the user web page by browsing to https://10.x.1.1/ccmuser. Log in with
username User5 and password cisco.
Step 8
Note
Go to User Options > User Settings and change the PIN to 54321.
The current PIN is 12345.
Explore User Web Page Options

Step 9
Go to User Options > Device, verify that Phone1-x is selected, and click Line
Settings.
Step 10
Verify that there is no option to change the Line Text Label.
Step 11
Log out from the user web pages using the Logout button at the top right corner of
the page.
Configure Available User Web Page Options

Step 12
Access the Cisco Unified Communications Manager web interface
(https://10.x.1.1/ccmadmin).
Step 13
Navigate to System > Enterprise Parameters and change the following settings in
the CCMUser Parameters section:
Show Line Text Label Settings: True
Show Change PIN Option: False
Re-verify User Web Page Options

Step 14
Access the user web page again. (Browse to https://10.x.1.1/ccmuser and log in with
username User5 and password cisco.)
Step 15
Try to change the PIN again. This is not possible now because the option is not
available at the User Settings Configuration page.
Step 16
Try to change the line text label for directory number 2001 to Phone1. This should
work now; the Line Text Label is part of the Line Settings Configuration.
Step 17
In Cisco Unified Communications Manager, go to User Management > End User

and click Find.
Step 18
Select User5 and change the PIN back to 12345.
Step 19
Click Save.
Cleanup
148
You configured the available options of the user web pages.
You logged into the user web pages and used some available options.
Note
Detailed verification was part of the activity procedure.

Lab Guide
149
Lab 5-3: Configuring Presence-Enabled Speed

Dials and Lists
Activity Objective
In this activity, you will configure Presence-enabled speed dials on 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
Lab 5-3: Configuring Presence-Enabled

Speed Dials and Lists
Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
Each phone
monitors status of
other two phones.
DHCP
10.x.2.0/24
PC-x
HQ-x .101
DHCP
10.x.3.0/24
.101
Enables Presence
Subscriptions.
.101
.2
10.x.1.0/24
CUCM2-x
Implements
Presence policies.
.1
.4
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.021
Required Resources
150
Cisco IP Phones
PC
Command List
Job Aids

In this task, you will configure Presence-enabled speed dials at phones Phone1-x to Phone3-x.
Each phone will watch the first lines of the other two phones.
Activity Procedure
Configure Phone Button Templates for the IP Phones
Step 1
Change the existing Customized 7961 phone button template to include Presenceenabled speed dial phone buttons (use buttons 5 and 6).
Step 2
Create a new Customized 7960 phone button template which includes Presenceenabled speed dial phone buttons (use buttons 5 and 6).
Step 3
Apply the newly create phone button template for 7960 IP phones to Phone1-x.
Configure Presence-Enabled Speed Dials at the IP Phones

Step 4
Configure phone buttons 5 and 6 at Phone1-x, Phone2-x, and Phone3-x to watch the
first directory number of the other two phones.
Verify the Need for Presence CSS
Step 5
Write down the partitions that are assigned to the first directory numbers of the
following phones:
Phone1-x: _____________________
Phone2-x: _____________________
Phone3-x: _____________________
Step 6
Note
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.

Lab Guide
151
Implement Subscribe CSS

Step 7
Create a CSS called CSS-LPM (LPM stands for Lobby-Phones, Phones, and
Manager-Phones) which includes all partitions discovered in Step 5.
Step 8
Assign the created CSS as a subscribe CSS to all three IP phones.
Step 9
Place calls between phones and verify that you now see Presence information on the
corresponding Presence-enabled speed dials.
Note
When implementing Presence in an environment that already has partitions in use (due to
calling privilege implementation), Presence is also affected by these partitions and therefore
subscribe CSS must be assigned even if no restrictions should be applied to Presence.
At all three phones, you see accurate Presence information at the Presence-enabled speed
dials.
Task 2: Implement Presence Policies

In this task, you will configure Presence-enabled call lists. They will only work at Phone2-x
and Phone3-x, but not at Phone1-x because the Cisco Unified IP Phone 7960 (Phone1-x) does
not support Presence-enabled call lists.
Activity Procedure
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
Place a call between a Cisco Unified IP Phone 7960 and a 7961. On the Cisco
Unified IP Phone 7961, browse through the missed calls list and verify that you do
not see any Presence information in the call list.
Step 3
Go to System > Enterprise Parameters and enable the BLF for Call Lists
enterprise parameter in Cisco Unified Communications Manager Administration.
Step 4
Repeat the previous test. This time you should be able to see Presence information at
the Cisco IP Phone 7961 when browsing through the list of missed calls.
Note
Presence-enabled call lists also require the subscribe CSS when the watched directory
numbers are in partitions. A subscribe CSS has been already assigned to all phones in the
previous task.
152
At Phone2-x and Phone3-x, you can view Presence information in call lists.

In this task, you will limit Presence visibility by implementing Presence policies. You will
configure subscribe CSS and Presence groups in order to control Presence subscriptions.
Activity Procedure
Implement Presence Policies
In this section, you will apply the following Presence policies:
Partitions: Lobby-Phones, Phones, Manager-Phones
CSSs:
CSS-LP includes partition Lobby-Phones
CSS-LPM includes partitions Lobby-Phones, Phones, and Manager-Phones
CSS-L includes partition Lobby-Phones
Presence groups: Group1, Group2, Group3
Presence group policies:
Group2 to Group3 permitted
Group3 to Group1 permitted
All other inter-Presence-group subscriptions denied
Phone1:Subscribe CSS: CSS-LP, Presence Group: Group2
Phone1, Line1: Partition Lobby-Phones, Presence Group: Group1
Phone2: Subscribe CSS: CSS-LPM, Presence Group: Group2
Phone2, Line1: Partition Phones, Presence Group: Group2
Phone3: Subscribe CSS: CSS-L, Presence Group: Group3
Phone3, Line1: Partition Manager-Phones, Presence Group: Group3
Note
The specified Presence policies are not a realistic example. They have only been chosen to
allow illustration on how Presence policies work.
Follow these steps to implement Presence policies for speed dials:

Step 1
Add CSSs CSS-LP and CSS-L and include partitions as described above.
Step 2
Add Presence groups Group1, Group2, and Group3.
Step 3
Configure inter-Presence group policies as described above. This is done by setting

the Cisco CallManager service parameter Default Inter-Presence Group
Subscription.
Step 4
Configure the phones with a subscribe CSS and Presence group as described above.

Lab Guide
153
Note
The previously configured subscribe CSS, CSS-LPM, is replaced by other subscribe CSSs
at Phone1-x and Phone3-x.
Step 5
Configure line 1 of the phones with the Presence groups as described above.
Step 6
Verify the Presence policies you implemented. You should get the following results:
Presence-enabled speed dial: Phone1 to x002: permitted
Presence-enabled speed dial: Phone1 to x003: denied
(Presence-enabled call list: Phone1 to x002: permitted)
Note
As Phone1 is a Cisco Unified IP Phone 7960, which does not support presence-enabled call
lists, you cannot verify the implemented Presence policy for call lists on this phone.
Presence-enabled call list: Phone1 to x003: denied
Presence-enabled call list: Phone2 to x001: denied
Presence-enabled call list: Phone2 to x003: permitted
Presence-enabled speed dial:Phone3 to x002: denied
Presence-enabled call list: Phone3 to x001: permitted
Presence-enabled call list:Phone3 to x002: denied
154
Presence subscriptions work as described in the activity procedure.
Lab 5-4: Integrating Cisco Unified

Communications Manager to Voice-Mail Systems
Activity Objective
In this activity, you will configure Cisco Unified Communications Manager to integrate with
Cisco Unity. After completing this activity, you will be able to meet these objectives:
Configure Cisco Unified Communications Manager for voice-mail integration
Configure Cisco Unified Communications Manager phones to send calls to voice mail
Configure Cisco Unity for integration with Cisco Unified Communications Manager
Configure Cisco Unity subscribers and voice-mail boxes
Visual Objective
Lab 5-4: Integrating Cisco Unified

Communications Manager to Voice-Mail
Systems
Phone1-x
Phone2-x
Phone3-x
Forwards to voice-mail.
Leaves voice-mail messages.
DHCP
DHCP
DHCP
Retrieves voice-mail
messages.
10.x.2.0/24
HQ-x .101
DHCP
10.x.3.0/24
.101
Configures voice-mail
integration.
.101
.2
10.x.1.0/24
.1
.4
CUCM2-x
Configures Cisco Unified

integration.
.102
HQ2-x
CUCM1-x
UNITY-x
CIPT1 v6.022
Required Resources
IP phones

Lab Guide
155
Cisco Unity
PC
Job Aids
Partitions for Voice-Mail Functionality
Partition Name
Description
Assigned to Devices
MWI
MWI On/Off for Voice Mail
MWI 8808
MWI 8809
VM
Hunt Pilot for Voice Mail
Hunt Pilot
8800
VM-Ports
VM Ports
DN /VM Port
8801
8802
Calling Search Spaces for Voice-Mail Functionality
Devices
Calling Search Space

Name
Description
Contains Partitions
Voice Mail Pilot

8800
To_VM_css
To Hunt Pilot 8800 from

Voice-Mail Pilot
VM
DN/VM Port
From_VM_css
To all phones, Local,

LD, MWI from Voice
Mail
MWI
8801
8802
Manager-Phones
Lobby-Phones
Phones
PSTN-Local_LD
MWI:
MWI_css
CSS to all phones
Lobby-Phones
8808
Manager-Phones
8809
Phones
Task 1: Configure Cisco Unified Communications Manager for

Voice-Mail Integration
In this task, you will configure Cisco Unified Communications Manager to integrate with Cisco
Unity.
156
Activity Procedure
Create New Partitions for Voice-Mail Functionality
Step 1
In Cisco Unified Communications Manager, go to Call Routing > Class of Control
> Partition and click Add New.
Step 2
Enter the following partitions and descriptions in the Partition Configuration

window in the shown format:
MWI, MWI On/Off for Voice Mail
VM, Hunt Pilot for Voice Mail
VM-Ports, VM Ports
Step 3
Click Save.
Create New Calling Search Spaces for Voice-Mail Functionality

Step 4
Go to Call Routing > Class of Control > Calling Search Space and click Add
New.
Step 5
In the Calling Search Space Configuration window, enter the following parameters:
Name: To_VM_css
Description: CSS to Hunt Pilot 8800
Step 6
Add partition VM to the CSS.
Step 7
Click Save.
Step 8
Repeat the previous steps for the two remaining calling search spaces listed in the
Calling Search Spaces for Voice Mail Functionality table in the Job Aid section.
Create MWI Extensions

Step 9
Go to Voice Mail > Message Waiting and click Add New.
Step 10
In the Message Waiting Configuration window, enter the following parameters:
Message Waiting Number: 8808
Partition: MWI
Description: MWI On
Set the Message Waiting Indicator radio button to: On
Calling Search Space: MWI_css
Step 11
Click Save and then click the Copy button
Step 12
Update the Message Waiting Number field to 8809, the Description field to MWI
Off, and set the radio button of the Message Waiting Indicator to Off.
Step 13
Click Save.

Lab Guide
157
Create Voice-Mail Ports

Step 14
Go to Voice Mail > Cisco Voice Mail Ports and click Add New.
Step 15
Step 16
Enter the following parameters in the Device Information pane:
Port Name: CiscoUM1-VI1
Description: First VM Port
Device Security Mode: Non Secure Voice Mail Port
Enter the following parameters in the Directory Number Information pane:
Directory Number: 8801
Partition: VM-Ports
Calling Search Space: From_VM_css
Step 17
Click Save.
Step 18
Click Copy and update the following parameters:
Step 19
Port Name: CiscoUM1-VI2
Description: Second VM Port
Update the following parameter in the Directory Number Information pane:
Step 20
Directory Number: 8802
Click Save.
Create a Line Group

Step 21
Go to Call Routing > Route/Hunt > Line Group and click Add New.
Step 22
Enter VM_LG as the Line Group Name.
Step 23
Select Top Down as the Distribution Algorithm.
Step 24
In the Available DN/Route Partition pane, select the newly created Voice Mail Port
8801/VM-Ports.
Step 25
Click Add to Line Group.
Step 26
Repeat the last two steps for the Voice Mail Port 8802/VM-Ports.
Step 27
Click Save.
Create a Hunt List
158
Step 28
Go to Call Routing > Route/Hunt > Hunt List and click Add New.
Step 29
Enter VM_HL in the Name field.
Step 30
Enter Voice Mail Hunt List in the Description field.
Step 31
For the Cisco Unified Communications Manager Group, select Default.
Step 32
Click the Enable this Hunt List and the For Voice Mail Usage check boxes.
Step 33
Click Save.
Step 34
In the Hunt List Member Information pane, click Add Line Group.
Step 35
In the new window Hunt List Detail Configuration, choose VM_LG from the Line
Group drop-down list.
Step 36
Click Save and then click OK on the popup window.
Create Hunt Pilot

Step 37
Go to Call Routing > Route/Hunt > Hunt Pilot and click Add New.
Step 38
Enter the following parameters in the Hunt Pilot Configuration window:
Hunt Pilot: 8800
Route Partition: VM
Description: Voice Mail Pilot
Hunt List: VM_HL
Step 39
Uncheck the Provide Outside Dial Tone check-box.
Step 40
Click Save.
Create Voice Mail Pilot

Step 41
Go to Voice Mail > Voice Mail Pilot and click Find.
Step 42
Enter the Default Pilot configuration by clicking Default in the Description column.
Step 43
In the Voice Mail Pilot Configuration window, enter the following parameters:
Step 44
Voice Mail Pilot Number: 8800
Calling Search Space: To_VM_css
Description: Default Voice Mail Pilot
Click Save.
Verify Voice-Mail Profile

Step 45
Go to Voice Mail > Voice Mail Profile and click Find.
Step 46
Enter the Default Mail Profile configuration by clicking Default in the Name
column.
Step 47
Verify that the Voice Mail Profile Name is Default and Voice Mail Pilot is
8800/To_VM_css. The Make This the Default Voice Mail Profile for the System
check-box must be activated.
Step 48
If you made any modifications, click Save.

Lab Guide
159
When you go to Call Routing > Class of Control > Partition and click the Find button,
the two new partitions VM_Ports and MWI_PT are shown in the result list.
When you go to Voice Mail > Cisco Voice Mail Ports and click Find, the voice-mail ports
CiscoUM1-VI1 and CiscoUM1-VI2 are shown in the result list.
When you go to Voice Mail > Message Waiting and click Find, two MWI entries are
shown in the result list, one for MWI On and one for MWI Off.
When you go to Voice Mail > Voice Mail Pilot and click Find, the Default Pilot shows the
Pilot Number 8800.
You have created a Line Group, Hunt List, and Hunt Pilot in Cisco Unified
Communications Manager.

Phones to Send Calls to Voice Mail
In this task, you will configure IP phones in Cisco Unified Communications Manager to
forward calls to voice mail.
Activity Procedure
Configure Phones to Use Voice Mail
Step 1
160
Step 2
Enter the Phone Configuration window for Phone1-x.
Step 3
Click the Line [1] link to enter the Directory Number Configuration window.
Step 4
Set the Voice Mail Profile in the Directory Number Settings pane to Default.
Step 5
In the Call Forward and Call Pickup Settings pane, activate the check boxes in the
Voice Mail column for the following Call Forward settings:
Forward Busy Internal
Forward Busy External
Forward No Answer Internal
Forward No Answer External
Forward Unregistered Internal
Forward Unregistered External
Step 6
Set the No Answer Ring Duration (seconds) field to 5 seconds.
Step 7
Click Save.
Step 8
Repeat the previous steps for Phone2-x and Phone3-x.
Add the Partition of the VM Pilot to the Phones CSS

Step 9
Go to Call Routing > Class of Control > Calling Search Space and click Find.
Step 10
Enter the calling search space Lobby_css and add partition VM to the CSS.
Step 11
Click Save.
Step 12
Repeat the previous steps for the CSSs Manager_css and Phones_css.
The specified Call Forward options in the Directory Number Configuration window for
Phone1-x and Phone2-x are set to Voice Mail.
Task 3: Configure Cisco Unity for Integration with Cisco

In this task, you will configure Cisco Unity to integrate with Cisco Unified Communications
Manager.
Activity Procedure
Step 1
Connect to the UNITY-x server (10.x.1.4) by using Microsoft Remote Desktop

client.
Step 2
Log in as user Administrator with password cisco.
Step 3
Go to Start > Programs > Unity > Manage Integrations.
Step 4
Click Create Integration.
Step 5
The Telephony Integration Setup Wizard window opens.
Step 6
Choose SCCP (CUCM/CCM and CUCME/CCME only) for the type of phone
system.
Step 7
Click Next.
Step 8
In the Integration Name field, enter CUCM1-x (where x is your pod number).
Step 9
Enter Pod-x for the Cluster Name and click Next.
Step 10
In the IP Address/Name field, enter the IP address of your publisher (10.x.1.1) and
click Next.
Step 11
In the Enter CUCM/CCM MWI extensions window, enter the previously created
MWI numbers:
Step 12
MWI on extension: 8808
MWI off extension: 8809
Click Next.

Lab Guide
161
162
Step 13
In the next window, leave all parameters with the default settings, and click
Verify to verify the connectivity to your Cisco Unified Communications Manager
publisher.
Step 14
After the test has been successful, click Next.
Step 15
Click Next at the next two windows and then click Finish to complete the
Telephony Integration Setup Wizard.
Step 16
Click Yes on the following popup windows, and wait until the Cisco Unity Services
are restarted (you will be notified by another popup window).
Verify if the integration was successful:
Step 1
Close the Manage Integrations window and reopen it by going to Start > Programs
> Unity > Manage Integrations.
Step 2
The new CUCM1-x integration shows under Cisco Unity server on the left side.
Check in the Cisco Unity Status Monitor web page if Cisco Unity is running:
Step 3
Open the shortcut on your desktop named Status Monitor or enter the URL
http://unity50/Web/SM/MainFrame.asp in your browser window (on the UNITYx server).
Step 4
The status should appear as Running.
Step 5
Click Port Status to verify if both configured ports are available.
Verify if you can reach Cisco Unity from the IP phones:
Step 6
From one of your IP phones, press the Messages key.
Step 7
Cisco Unity should answer the call.
Step 8
End the call.
Task 4: Configure Cisco Unity Subscribers and Voice-Mail

Boxes
In this task, you will configure Cisco Unity voice-mail boxes for subscribers.
Activity Procedure
Step 1
In your Microsoft Remote Desktop Client connection to UNITY-x, go to the Unity

System Administration web page on the Cisco Unity server by browsing to the
following URL: http://unity50/Web/SA/FrameASP/StartFrame.asp.
Step 2
On the left, click Subscribers.
Step 3
Click Add Subscriber, the + icon.
Step 4
Configure the following settings for the new subscriber:
First name: Phone1
Last name: User1
Display name: Phone1
Extension: 2001
Alias: User1

Lab Guide
163
Step 5
Click Add, and a new window appears.
Step 6
In the Active Schedule field, click All Hours - All Days.
Step 7
Click on the floppy icon to save your changes.
Step 8
Click Phone Password on the left.
Step 9
Set the phone password to 26543 and click on the floppy icon to save.
Step 10
Repeat the previous steps for the other two phones (Phone2 and Phone3), varying
the appropriate values.
Verify that the IP phones are recognized by Cisco Unity:
Step 1
From one of your Cisco IP phones, press the Messages key.
Step 2
Cisco Unity answers the call and asks for the password.
Step 3
Enter 26543 for the password and press the pound key (#).
Step 4
Cisco Unity will now start the self-enrollment to configure your voice mail. Follow
the instructions, and when completed, end the call.
Verify if voice mail is working:
Step 5
Place a call from Manager Phone (2003) to Phone1-x (with directory number 2001).
Step 6
Do not answer the call at Phone1-x; wait until Cisco Unity answers the call.
Step 7
Leave a message after the beep tone and hang up.
Step 8
Wait until the MWI light turns red at Phone1-x.
Step 9
Press the Messages key at Phone1-x and authenticate the user with the password
26543.
Step 10
You should now be able to listen to the new messages left by Phone3-x.
Note
Step 11
164
You have to go through the enrollment process if not done in the previous task, in order to
be able to access your messages.
Hang up, the MWI light turns off.

Activity Objective
In this activity, you will use Cisco Unified Video Advantage to make video telephony calls.
After completing this activity, you will be able to meet these objectives:
Enable video capabilities on the Cisco IP phones
Install Cisco Unified Video Advantage
Check Cisco Unified Video Advantage connections and video signal quality
Configure the maximum bandwidth for a video call
Visual Objective
Lab 5-5: Enabling Cisco Unified Video

Advantage
Phone1-x
Phone2-x
DHCP
Phone3-x
DHCP
Install Cisco Unified Video

Advantage on PCs.
Attach Cisco VT Advantage
Cameras to PCs.
DHCP
10.x.2.0/24
Guest
PC
Place video call.
PC-x
HQ-x .101
DHCP
DHCP
10.x.3.0/24
.101
.101
.2
10.x.1.0/24
Enable video capabilities for

Cisco IP phones.
CUCM2-x
.1
.4
.102
HQ2-x
CUCM1-x
UNITY-x
Note
CIPT1 v6.023
The PC-x Ethernet port is physically connected to the PC port of Phone1-x.
Required Resources

Lab Guide
165
IP phones
PCs with Cisco VT Camera
The lab devices shown in the Visual Objectives figure are detailed in the table.
Device
CUCM1-x
Cisco Unified Communications Manager publisher that

serves the IP phones
PC-x
PC
Cisco VT Camera
Video camera attached to the PC-x for video calls
Phone1-x
Video-enabled IP phone that has PC connected to it
The table gives the device credentials to log in to the lab devices that require
authentication.
Credentials for Device Access

Device
Username and Password
CUCM1-x Platform Administration
admin
adminpass
Cisco Unified Cisco Unified

Administration
CCMAdministrator
appuserpass
Command List
Job Aids
The table gives the directory number needed to place calls in the lab activity.
Directory Number
166
Device
Directory Number
Phone1-x
2001
Phone2-x
2002
The lab devices use the IP address allocation scheme shown in the table.
Parameter
Value
10.x.1.0/24
Data network
10.x.3.0/24
Default gateways
CUCM1-x
10.x.1.1/24
PC-x
Task 1: Enabling Video Capabilities

In this task, you will enable the IP phones to support video calls when they are connected to an
appropriately equipped PC. You will enable the video capabilities of Phone1-x and Phone2-x.
Activity Procedure
Step 1
From PC-x, access Cisco Unified Communications Manager Administration on

CUCM1-x. Go to Device > Phone and list all phones.
Step 2
Click Phone1-x.
Step 3
Scroll down to the bottom of the Phone Configuration window and in the Video
Capabilities drop-down menu, choose Enabled.
Step 4
Verify that the PC port is enabled.
Step 5
Click Save and reset the phone.
Step 6
Repeat the above procedure for Phone2-x.
Phone1-x and Phone2-x show the video camera icon at the bottom right corner of their
screen.
Task 2: Installing Cisco Unified Video Advantage

In this task, you will install Cisco Unified Video Advantage on PC-x.
Activity Procedure
Step 1
Ensure that the camera is not yet plugged into a USB port at PC-x. Do not plug it in
unless instructed to do so.

Lab Guide
167
Step 2
At PC-x, start the Cisco Unified Video Advantage client installation application
(CiscoUnifiedVideoAdvantageSetup.exe), which is stored at the desktop of PC-x.
Note
Step 3
If you cannot locate the software, ask your instructor for help.
Follow the instructions of the installation routine and install Cisco Unified Video
Advantage with default settings.
Note
You may have to restart your system after installation.
Step 4
After the installation (and after restarting the PC, if needed), Cisco Unified Video
Advantage launches automatically. Double-click the corresponding icon in the
system tray of PC-x to verify that Cisco Unified Video Advantage is running.
Step 5
Plug the camera into a USB port at PC-x. The hardware is detected automatically.
Step 6
Minimize the Cisco Unified Video Advantage application window.
Cisco Unified Video Advantage is running on PC-x.
Task 3: Checking the Cisco Unified Video Advantage

Connections and Video Signal Quality
In this task, you will use tools built into Cisco Unified Video Advantage to check connectivity
to the IP phone and verify good signal quality.
Activity Procedure
168
Step 1
At PC-x, double-click the Cisco Unified Video Advantage icon in the system tray.
Step 2
In the Cisco Unified Video Advantage application window, go to the Video menu
and choose the Video Check menu item to start the video check.
Step 3
You should see two windows, both showing the same image: the view of your
camera. One window is called Local and the other window is called Remote.
Step 4
Check the video signal indicators in the local and remote views. The strongest
possible signal is shown by a solid green bar. The poorest signal quality is shown by
a solid gray bar.
Step 5
Stop the video check by going to the Cisco Unified Video Advantage application
and choosing the menu item Video Check in the Video menu.
Step 6
Disconnect the Ethernet cable connected at the back of the PC (or at the PC port on
the back of Phone1-x). In the Cisco Unified Video Advantage main window,
observe that the connecting line between the IP phone and the camera turns into a
red broken link (instead of a solid green link).
Step 7
Plug the Ethernet cable back in. After a few moments the red broken link should
turn back to a solid green link.
You have completed this task if all tests during the activity procedure succeeded. No specific
verifications are needed.
Task 4: Configuring the Maximum Bandwidth for a Video Call

In this task, you will set the maximum video call bandwidth per call to 384 kbps in Cisco
Unified Communications Manager region configuration.
Activity Procedure
Step 1
From PC-x, access Cisco Unified Communications Manager Administration on

CUCM1-x. Go to System > Region and click Find.
Step 2
Click the Default region. In the configuration window for this region, verify that the
maximum voice codec per call is set to G.711 and the maximum video call
bandwidth per call is set to 384 kbps. Click Save and restart the associated devices,
using the Reset button.
You are able to place a video call between the two phones where Cisco Unified Video
Advantage has been enabled. Specifically, perform these steps.
Step 1
Note
Step 2
Add a second PC running Cisco Unified Video Advantage (with the software
installed and the camera attached) to your cluster. Connect the PC-to-PC port of
Phone2-x.
Because you only have one PC per cluster, work together with the students of a second pod
by sharing your laptops. Attach a second laptop to each cluster (connect it to Phone2-x) and
then place a call between these two phones. Then move the two PCs to the other pod.
Place a call from Phone1-x to Phone2-x. At the attached PCs, a video screen should
pop up. You should now have the audio connection between the two Cisco IP
phones and the video connection between the two PCs.

Lab Guide
169
170
Answer Key
The correct answers and expected solutions for the activities that are described in this guide
appear here.
Lab 1-1 Answer Key: Cisco Unified Communications Manager

Installation and Upgrade Discovery
Task 1: Install Cisco Unified Communications Manager Publisher
When the Cisco Unified Communications Manager installation is completed, the following
window appears:
After successful login, start the ping as shown in the window:

Lab Guide
171
To access the Cisco Unified Communications Manager GUI, accept the Cisco Unified
Communications Manager certificate by clicking Yes at the Security Alert window:
Login with CCMAdministrator user account and appuserpass as password:
172
Task 2: Install Cisco Unified Communications Manager Subscriber

When the Cisco Unified Communications Manager installation is completed, the following
window appears:
After successful login, start the ping as shown in the window:
In the Cisco Unified Communications Manager GUI, after navigating to System > Cisco
Unified CM, and after clicking Find, the following window appears:
Lab 2-1 Answer Key: Exploring Cisco Unified Communications

Manager Administration Options
When you complete this activity, your results will be similar to the results here, with
differences that are specific to your device or workgroup:
Task 1: Access the Cisco Unified Communications Manager Administration Window

After successful login to the Cisco Unified Communications Manager web GUI, the following
screen is shown:

Lab Guide
173
Q1)
You can find the Partition menu item in the Call Routing > Class of Control > Partition menu, and the
Calling Search Space menu item in the Call Routing > Class of Control > Calling Search Space menu.
Q2)
You can find the Enterprise Parameters option in the System > Enterprise Paramerters menu.
Q3)
You can find registered IP phones in the Device > Phone menu.
Q4)
You can add end users in the User Management > End User menu.
Q5)
You can configure the MOH Audio Source in the Media Resources > Music On Hold Audio Source
menu.
To log in to the different administration pages, you can use the navigation bar as shown in the
following window:
174

The following screen appears when you navigate to Tools > Control Center - Network
Services:
Q6)
Service Activation, Control Center Feature Services, Control Center Network Services, Serviceability
Reports, CDR Management.
Q7)
All of them (Cisco CallManager Serviceability RTMT, Cisco RTMT Reporter Servlet, Cisco Log Partition
Monitoring Tool, Cisco Tomcat Stats Servlet, Cisco RIS Data Collector, and Cisco AMC Service).
Q8)
The answer to this question depends on when the Cisco unified Communications Manager in this lab
environment was installed.

Lab Guide
175
176
Q1)
Navigate to Show > Cluster menu to see the cluster information:
Q2)
Navigate to Show > Hardware menu
Q3)
Navigate to Show > Network menu
Q4)
Navigate to Show > Software menu
Q5)
Navigate to Services > Ping menu
Q6)
Navigate to Services > Remote Support menu:

Q1)
When the question mark ? is entered on CLI, these commands are listed:
admin:?
help
quit
show*
set*
delete*
unset*
file*
utils*
run*

Lab Guide
177
Q2)
The following commands and information are shown by entering the show ? command and show network
eth0 command:
admin:show ?
show status
show logins
show hardware
show workingdir
show web-security
show smtp
show myself
show account
show registry
show trace
show ups*
show environment*
show memory*
show open*
show timezone*
show cert*
show ipsec*
show version*
show packages*
show network*
show stats*
show firewall*
show process*
show tech*
show risdb*
show perf*
admin:show network eth0
Ethernet 0
DHCP
: disabled
Status
: up
IP Address
: 10.1.1.1
IP Mask
: 255.255.255.000
Mode
: Auto disabled,
Link Detected: yes

N/A, N/A
Duplicate IP : no
DNS
178
Primary
Secondary
Options
Domain
Gateway
: 10.1.1.101 on Ethernet 0
admin:
Q3)
To see the active and inactive version of Cisco Unified Communications Manager, enter the following
commands:
show version active, show version inactive
Q4)
The Cisco Unified Communications Manager Release 6.0.1.2003-3 should be active:
admin:show version active

Active Master Version: 6.0.1.2000-3
Active Version Installed Software Options:

No Installed Software Options Found.
Lab 2-2 Answer Key: Configuring Cisco Unified

When you complete this activity, your results will be similar to the results here, with

To upload the license file, go to System > Licensing > License File Upload, click Upload
License File, and choose the correct .lic file from your local directory:

Lab Guide
179
The License File Information box shows the license file that you uploaded:

When you go to System > Server and click Find, the result list should show as the following:
Verify in the System > Enterprise Parameters menu that all entries in the Phone URL
Parameters pane do not contain any DNS names (CUCM1-x).

In the System > Cisco Unified CM menu, the following window appears:
180
In the Cisco Unified Serviceability Administration GUI, the Cisco CallManager, Cisco TFTP,
and Cisco DHCP Monitor services must be started in the CM Services pane, under Control
Center Feature Services:
Task 4: Configure Cisco Unified Communications Manager to Provide DHCP

Services
The DHCP Server is configured in System > DHCP > DHCP Server, as shown in the
following screen:

Lab Guide
181
The DHCP Subnet is configured in System > DHCP > DHCP Subnet, as the following
window shows:
Task 5: Configure Cisco Unified Communications Manager Enterprise and Service

Parameters
The Dependency Records parameter is enabled in System > Enterprise Parameters, as shown
in the following window:
The CDR and CMR parameters are enabled in System > Service Parameters from the
publisher server in the Cisco CallManager service (from the drop-down list), as shown in the
following window:
182
Lab 2-3 Answer Key: Managing User Accounts in Cisco Unified

The Verification sections within the tasks provide all the verification that is needed.
Lab 3-1 Answer Key: Configuring Voice VLANs

When you complete this activity, your configuration will be similar to the results here, with
Task 1: Discovering the Cisco Catalyst IOS Switch Configuration

Output of the show power inline command:
show power inline
Available:360(w)
Interface Admin
Used:18(w)
Oper
Remaining:342(w)
Power
Device
Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ---Fa0/5
auto
on
6.3
IP Phone 7960
n/a
15.4
Fa0/6
auto
on
6.3
IP Phone 7961
15.4
Fa0/7
auto
on
6.3
IP Phone 7961
15.4
Lab 3-2 Answer Key: Implementing IP Phones


Lab Guide
183
Lab 3-3 Answer Key: Hardening IP Phones

At Phone1-x, only the Contrast and Ring Type menus are available under Settings. At Phone3x, no settings can be accessed. Network settings cannot be viewed on any of the phones.
Lab 4-1 Answer Key: Implementing MGCP Gateways

MGCP Gateway HQ-x configuration:
ccm-manager redundant-host 10.1.1.2
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 10.1.1.1
ccm-manager config
!
mgcp call-agent 10.1.1.1 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
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 package-capability fxr-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
!
mgcp profile default

Communications Manager Call Routing Components
When you complete this activity, your HQ1-x debug outputs will be similar to the results here,
with differences that are specific to your device or workgroup:
HQ-1#
*Sep 26 14:27:37.054: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8
callref = 0x0012
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
184
Transfer Mode = Circuit

Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x0181, '2002'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x80, '18005551234'
Plan:Unknown, Type:Unknown
Cisco DNA output will be similar to the following:

+ Results Summary
- Call Flow
+ Route Pattern :Pattern= 9.!
- Route List :Route List Name= RL_MGCP_GWs
- RouteGroup :RouteGroup Name= RG_MGCP_GWs
PreTransform Calling Party Number = 2002
PreTransform Called Party Number = 911
Calling Party Transformations
Called Party Transformations
- Device :Type= MGCPT1PRIPort
- Device :Type= MGCPT1PRIPort
End Device Name = S0/SU0/DS1-0@HQ-1
PortNumber = 0
Device Status = UnKnown
AAR Group Name =
AAR Calling Search Space =
AAR Prefix Digits =
Call Classification =
Calling Party Selection =
CallingLinePresentation =
ConnectedLinePresentation =
Number Of Strip Digits =
CallerID DN =
+ Alternate Matches
Lab 4-3 Answer Key: Implementing Digit Manipulation


Lab Guide
185
Lab 4-4 Answer Key: Implementing Calling Privileges in Cisco

Lab 4-5 Answer Key: Implementing Call Coverage in Cisco

When you complete this activity, your solution will be similar to this, with differences that are
specific to your device or workgroup.

Step 5
What do you expect will happen when you call the hunt pilot from 2004?
The call should hunt immediately to directory number 2002 because the hunt option for
busy is set to Try Next Member; Then, Try Next Group in Hunt List. After Phone2-x
rings for 5 seconds, hunting exhausts because no final forwarding is configured.
Task 5: Configuring Final Forwarding for Busy and No-Answer Conditions

Step 10
The call will ring 2003 first, after 5 seconds the call hunts to 2001, after 5 seconds the
call hunts to 2002, after 2 seconds (maximum hunt timer of 12 seconds is expired) the
call is forwarded to the final destination of 2001.
Step 11
Hunting starts at the first member of the first line group (that is, 2003) due to the topdown distribution algorithm at the line group. Because the busy trigger has been set
back to 2 for this line, the phone indicates the additional call. After 5 seconds, the next
line group member is tried (based on the configured hunt option for the no answer
condition). However, the next line (2001) is in a call and has a busy trigger of 1.
Therefore it fails with a busy condition. As the hunt option for busy is set to Try Next
Member, But Do Not Go To Next Group, the second line group (with member 2002) is
skipped and hunting fails with a busy condition. Therefore, the final forwarding setting
for busy must be used. Because the final forwarding destination for busy is 2003, the
result is that after Phone3-x rings for 5 seconds (during hunting), the call is forwarded
immediately after these 5 seconds.
Lab 5-1 Answer Key: Implementing Media Resources

When you complete this activity, your solution will be similar to this, with differences that are
specific to your device or workgroup.

The output of the show sccp command used in the activity verification should look like the
following:
SCCP Admin State: UP
186
Gateway IP Address: 10.1.1.101, Port Number: 2000

IP Precedence: 5
User Masked Codec list: None
Call Manager: 10.1.1.1, Port Number: 2000
Priority: N/A, Version: 3.1, Identifier: 1
Conferencing Oper State: ACTIVE - Cause Code: NONE

Active Call Manager: 10.1.1.1, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 1
Reported Max Streams: 16, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
Supported Codec: rfc2833 dtmf, Maximum Packetization Period:
30
Supported Codec: rfc2833 pass-thru, Maximum Packetization
Period: 30
Supported Codec: inband-dtmf to rfc2833 conversion, Maximum
Packetization Period: 30
The output of the show sccp ccm group 1 command used in the activity verification should
look like the following:
CCM Group Identifier: 1
Description: None
Binded Interface: NONE, IP Address: NONE
Associated CCM Id: 1, Priority in this CCM Group: 1
Associated CCM Id: 2, Priority in this CCM Group: 2
Associated Profile: 1, Registration Name: HW-CFB_HQ-1
Registration Retries: 3, Registration Timeout: 10 sec
Keepalive Retries: 3, Keepalive Timeout: 30 sec
CCM Connect Retries: 3, CCM Connect Interval: 10 sec
Switchover Method: GRACEFUL, Switchback Method:
GRACEFUL_GUARD
Switchback Interval: 10 sec, Switchback Timeout: 7200 sec
Signaling DSCP value: cs3, Audio DSCP value: ef
The output of the show dspfarm profile 1 command used in the activity verification should
Dspfarm Profile Configuration
Profile ID = 1, Service = CONFERENCING, Resource ID = 1

Profile Description :
Lab Guide
187
Profile Admin State : UP

Profile Operation State : ACTIVE
Application : SCCP
Status : ASSOCIATED
Resource Provider : FLEX_DSPRM
Status : UP
Number of Resource Configured : 2

Number of Resource Available : 2
Codec Configuration
Codec : g711ulaw, Maximum Packetization Period : 30 ,
Transcoder: Not Required
Codec : g711alaw, Maximum Packetization Period : 30 ,
Transcoder: Not Required

The output of the show dspfarm dsp active command used in the activity verification should
SLOT DSP VERSION STATUS CHNL USE
TYPE RSC_ID
BRIDGE_ID
1.1.1
UP
USED
conf 1
48
1.1.1
UP
USED
conf 1
49
1.1.1
UP
USED
conf 1
50
Total number of DSPFARM DSP channel(s) 1

Lab 5-3 Answer Key: Configuring Presence-enabled Speed

Dials and Lists
Lab 5-4 Answer Key: Integrating Cisco Unified

Communications Manager to Voice Mail Systems
Lab 5-5 Answer Key: Enabling Cisco Unified Video Advantage

188

CIPT160LG Secured PDF

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CIPT160LG Secured PDF

Transféré par

Droits d'auteur :

Formats disponibles

CIPT1

Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT) v6.0

2008 Cisco Systems, Inc.

Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT) v6.0

Task 1: Enabling Video Capabilities

Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT) v6.0

2008 Cisco Systems, Inc.

Lab 2-1: Exploring Cisco Unified Communications Manager Administration Options

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

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

Lab 3-1: Configuring Voice VLANs

Lab 3-2: Implementing IP Phones

Lab 3-3: Hardening IP Phones

Lab 4-1: Implementing MGCP Gateways

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 5-2: Configuring Cisco Unified Communications Manager User Features

Lab 5-3: Configuring Presence-Enabled Speed Dials and Lists

Lab 5-4: Integrating Cisco Unified Communications Manager to Voice-Mail Systems

Lab 5-5: Enabling Cisco Unified Video Advantage

Lab 1-1: Cisco Unified Communications Manager

Install a Cisco Unified Communications Manager publisher

Install a Cisco Unified Communications Manager subscriber

Lab 1-1: Cisco Unified Communications

Install Cisco Unified

Install Cisco Unified

2008 Cisco Systems, Inc. All rights reserved.

Cisco Unified Communications Manager Release 6.0 publisher

Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0

2008 Cisco Systems, Inc.

Lab Devices and Their Roles

Device Role in the Activity

Cisco Unified Communications Manager Release 6.0

Cisco Unified Communications Manager Release 6.0

PC with Internet Explorer browser

Cisco Unified Communications

Cisco Unified Communications

Voice server network

HQ-x: Node address .101 (for all networks)

Task 1: Install Cisco Unified Communications Manager

2008 Cisco Systems, Inc.

Start the installation and perform the media check.

Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0

2008 Cisco Systems, Inc.

Click Proceed to start the Platform Installation Wizard.

2008 Cisco Systems, Inc.

Click No in the Apply Patch window.

Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0

2008 Cisco Systems, Inc.

2008 Cisco Systems, Inc.

Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0

2008 Cisco Systems, Inc.

2008 Cisco Systems, Inc.

In the DNS Client Configuration window, click No.

In the Administrator Login Configuration window enter the administrator ID admin

Implementing Cisco Unified Communications IP Telephony Part 1 (CIPT1) v6.0

2008 Cisco Systems, Inc.

In the Certificate Information window, enter the company information as shown.

2008 Cisco Systems, Inc.

In the Network Time Protocol Client Configuration window, click No to continue