CIPT1
Cisco IP Telephony
Part 1
Volume 1
Version 4.1

Student Guide

CLS Production Services: 08.18.05
Copyright  2005, Cisco Systems, Inc. All rights reserved.
Cisco Systems has more than 200 offices in the following countries and regions. Addresses, phone numbers, and
fax numbers are listed on the Cisco Website at www.cisco.com/go/offices.

Argentina • Australia • Austria • Belgium • Brazil • Bulgaria • Canada • Chile • China PRC • Colombia • Costa
Rica
Croatia • Cyprus • Czech Republic • Denmark • Dubai, UAE • Finland • France • Germany • Greece
Hong Kong SAR • Hungary • India • Indonesia • Ireland • Israel • Italy • Japan • Korea • Luxembourg • Malaysia
Mexico • The Netherlands • New Zealand • Norway • Peru • Philippines • Poland • Portugal • Puerto Rico •
Romania
Russia • Saudi Arabia • Scotland • Singapore • Slovakia • Slovenia • South Africa • Spain • Sweden • Switzerland
Taiwan • Thailand • Turkey • Ukraine • United Kingdom • United States • Venezuela • Vietnam • Zimbabwe

Copyright  2005 Cisco Systems, Inc. All rights reserved. CCSP, the Cisco Square Bridge logo, Follow
Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live,
Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST,
BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo,
Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering
the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare,
GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness
Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network
Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet,

Cisco AVVID 1-4
Cisco CallManager Functions 1-5
Example: Basic IP Telephony Call 1-7
Cisco CallManager Operating System, Database, and Supporting Applications 1-8
Cisco CallManager Servers 1-9
Installation CD-ROMs 1-10
Installation Configuration Data 1-11
Example: Configuration Data Worksheet 1-13
Postinstallation Procedures 1-15
Activating Cisco CallManager Services 1-17
Upgrading Prior Cisco CallManager Versions 1-20
Summary 1-21
References 1-22
Identifying Cisco CallManager Cluster and Deployment Options 1-23
Overview 1-23
Objectives 1-23
Microsoft SQL Cluster Relationship 1-25
Intracluster Communication 1-27
Cluster Redundancy Designs 1-28
Call-Processing Deployment Models 1-30
Single-Site Deployment 1-31
Multisite WAN with Centralized Call Processing 1-34
Multisite WAN with Distributed Call Processing 1-36
Clustering over the IP WAN 1-39
Summary 1-41
References 1-42
Module 1 Summary 1-43
Module 1 Self-Check 1-44
Module 1 Self-Check Answer Key 1-46
Establishing an On-Cluster Call 2-1

Catalyst Switch Role in IP Telephony 2-36
Powering the Cisco IP Phone 2-37
Types of PoE Delivery 2-38
Catalyst Family of PoE Switches 2-41
Configuring PoE 2-43
Configuring Dual VLANs 2-45
Configuring Class of Service 2-50
Summary 2-52
References 2-53
Configuring Cisco IP Communicator 2-55
Overview 2-55
Objectives 2-55
Cisco IP Communicator Overview 2-56
Cisco IP Communicator Installation and Configuration Overview 2-59
Configuring Cisco CallManager for Cisco IP Communicator 2-60
Deploying and Updating Cisco IP Communicator 2-61
Postinstallation Configuration Tasks 2-64
Summary 2-65
References 2-66
Using the Bulk Administration Tool 2-67
Overview 2-67
Objectives 2-67
Introducing the Bulk Administration Tool 2-68
Installing BAT 2-72
Using the BAT Wizard 2-74
Configuring BAT Templates 2-78
Creating CSV Files 2-81
Validating Data Input Files 2-85
Inserting IP Phones into Cisco CallManager 2-86
Updating IP Phones with BAT 2-87

Switched Networks (BCMSN)
Ability to configure and operate Cisco
routers and switches and to enable
VLANs and DHCP
Interconnecting Cisco Network
Devices (ICND)
Cisco CCNA
®
certification
recommended prerequisite
Working knowledge of fundamental terms
and concepts of computer networking, to
include LANs, WANs, and IP switching
and routing
Cisco Learning OfferingSkill or Knowledge

Course Goal and Objectives
This topic describes the course goal and objectives.
©2005 Cisco Systems, Inc. All rights reserved. CIPT1 v4.1—4
“To prepare learners to install, configure, and
maintain a Cisco IP telephony solution. The
course focuses on the Cisco CallManager,
which is the call routing and signaling
component for the Cisco IP telephony
solution.”
Cisco IP Telephony Part 1
Course Goal

Upon completing this course, you will be able to meet these objectives:
n Deploy a Cisco CallManager server in a cluster by using a supported IP telephony

an On-Cluster
Call
Establishing
an Off-Cluster
Call
Enabling
Features and
Services
A
M
P
M
Wrap-Up
Day 1 Day 2 Day 3 Day 4 Day 5
Establishing
an On-Cluster
Call
Establishing
an Off-Cluster
Call
Establishing
an Off-Cluster
Call
Establishing
an On-Cluster
Call
Enabling
Features
and Services
Configuring

Gateway
SwitchSwitch
PSTN
CO Switch
LDAP
Directory
Server
Relational
Database
DSP
Digital Signal
Processor
VLAN or Cluster
(Color May Vary)
File
Server

©2005 Cisco Systems, Inc. All rights reserved. CIPT1 v4.1—7
PC
Fax
Printer
WAN
Telecommuter
Mobile User
Course Icons and Symbols (Cont.)
Building
Building
Laptop
Videoconference
Video

(IPTT)
Implementing Cisco Quality of
Service (QOS)
Cisco IP Telephony Part 1
Cisco IP Telephony Part 2
Cisco Voice Over IP
CVOICE 642-
432
Expert
Expand Your Professional Options
and Advance Your Career
Cisco Voice Career Certifications
Professional-level recognition in Cisco Voice Career
Certifications
Gateway
Gatekeeper
Implementing Cisco Voice Gateways
and Gatekeepers

You are encouraged to join the Cisco Certification Community, a discussion forum open to anyone
holding a valid Cisco Career Certification (such as Cisco CCIE
®
, CCNA
®
, CCDA
®
, CCNP
®
, CCDP
®

CallManager.
This lesson discusses the Cisco Architecture for Voice, Video and Integrated Data (AVVID) and Cisco
CallManager functions, hardware requirements, software requirements, and installation and upgrade
information.
Objectives
Upon completing this lesson, you will be able to identify the functions that Cisco CallManager provides
in the overall Cisco AVVID strategy and identify the hardware, software, and tasks required for a Cisco
CallManager installation.
This ability includes being able to meet these objectives:
n Describe the purpose and key components of each Cisco AVVID layer
n Identify the primary Cisco CallManager functions
n Identify the software that Cisco CallManager depends upon for its operating system,
database, directory, and backup
n Identify the major features of each base platform on which Cisco CallManager Release 4.1
is supported
n Identify the Cisco CallManager CDs that are required for installation
n Identify all configuration data that is required to install Cisco CallManager software
n Perform postinstallation procedures to help secure the server and optimize server resources
n Activate Cisco CallManager services
n Identify the supported versions of Cisco CallManager required to upgrade to release 4.1
Cisco AVVID
This topic describes the purpose and key components of each Cisco AVVID layer.
©2005 Cisco Systems, Inc. All rights reserved. CIPT1 v4.1—1-3
Cisco AVVID
D
i
s
t
r
i

O
p
e
n
Cisco CallManager
Call Admission, Call Routing
Call Processing
Applications
TAPI, JTAPI, SMDI
Cisco IPCC
Cisco Unity
Gateway
Router Switch
Infrastructure
Cisco IOS Network Services
IP Phone
Cisco IP Communicator
PC
Video
Client
Directory

applications

Cisco CallManager extends enterprise telephony features and functions to packet telephony network
devices. These network devices include Cisco IP Phones, media-processing devices, voice over IP
(VoIP) gateways, and multimedia applications. Additional data, voice, and video services, such as
converged messaging, multimedia conferencing, collaborative contact centers, and interactive
multimedia response systems, interact with the IP telephony solution through the Cisco CallManager
application programming interface (API).
Cisco CallManager provides the following functions:
n Call processing: Call processing refers to the complete process of routing, originating, and
terminating calls, including any billing and statistical collection processes.
n Signaling and device control: Cisco CallManager sets up all of the signaling connections
between call endpoints and directs devices such as phones, gateways, and conference bridges
to establish and tear down streaming connections.
n Dial plan administration: The dial plan is a set of configurable lists that Cisco
CallManager uses to determine call routing. Cisco CallManager provides the ability to create
secure dial plans for users.
n Phone feature administration: Cisco CallManager extends services such as hold, transfer,
forward, conference, speed dial, last-number redial, Call Park, and other features to IP
Phones and gateways.
n Directory services: Cisco CallManager uses DC-Directory as an embedded Lightweight
Directory Access Protocol (LDAP) directory. This directory stores authentication and
authorization information about users and is a standard feature of Cisco CallManager (it
does not require any special configuration or installation). However, Cisco CallManager can
also be integrated with a corporate LDAP directory.
n Programming interface to external applications: Cisco CallManager provides a
programming interface to external applications such as Cisco IP SoftPhone, Cisco IP
Interactive Voice Response (IVR), Cisco Personal Assistant, and Cisco CallManager
Attendant Console.
©2005 Cisco Systems, Inc. All rights reserved. CIPT1 v4.1—1-5

and Supporting Applications
This topic identifies key software on which Cisco CallManager depends.
©2005 Cisco Systems, Inc. All rights reserved. CIPT1 v4.1—1-6
Operating System, Database, and
Applications
• Windows 2000 Server
• Microsoft SQL Server 2000
• DC-Directory
• Cisco IP Telephony Backup and Restore System

Cisco CallManager server relies on Microsoft Windows 2000 for its operating system and Microsoft
Structured Query Language (SQL) Server 2000 for its database (both provided by Cisco Systems). The
operating system version that Cisco provides is called the Cisco IP Telephony Operating System. Cisco
CallManager 4.1(2) requires Cisco IP Telephony Operating System Version 2000.2.6 (or later) and the
latest Cisco IP Telephony Server Operating System service release (2000-2-6 sr3 or later). Cisco
CallManager 4.1(3) requires Cisco IP Telephony Operating System Version 2000.2.7 (or later) and the
latest service release (2000-2-7 sr2 or later).
Cisco CallManager uses DC-Directory as an embedded LDAP directory. This directory stores
authentication and authorization information about users and is standard with Cisco CallManager (it
does not require any special configuration or installation). Authentication establishes the right of the
user to access the system, while authorization identifies the telephony resources that a user is permitted
to use, such as a specific telephone extension.
The Cisco Customer Directory Plugin allows you to integrate Cisco CallManager with one of the
following enterprise directories:
n Microsoft Active Directory, available with Microsoft Windows 2000
n Microsoft Active Directory, available with Microsoft Windows 2003
n Netscape Directory Server, Versions 4.1 and 4.2,
n Sun ONE Directory Server 5.x
The Cisco IP Telephony Backup and Restore System (BARS) can be used to back up Cisco
CallManager. Cisco BARS is installed separately from Cisco CallManager.

2U Rack
Mount
MCS 7835-I1
100011Pentium 4 3400 MHz
1U Rack
Mount
MCS 7825-I1
30011Pentium 4 3060 MHzTowerMCS 7815-I1
Max. Phones
Per Cluster
CPU
Max.
CPU EquippedProcessorSpacePlatform

Because voice networks should maintain an uptime of 99.999 percent, you must install Cisco
CallManager on a server that meets Cisco configuration standards. For this reason, Cisco has
collaborated with two server hardware manufacturers, Hewlett-Packard and IBM, to create Cisco Media
Convergence Servers (MCSs). Hewlett-Packard and IBM designed these server hardware platforms
specifically for Cisco voice applications.
All of these servers are rack-mountable and do not include a monitor, mouse, or keyboard. Cisco
designed the Cisco MCS for local setup, rack mounting, and remote administration.
For a list of servers on which Cisco CallManager 4.1 is supported, refer to the Cisco CallManager 4.1
data sheet at:
/>0.html.
Installation CD-ROMs
This topic identifies the CD-ROMs that you must use to install a Cisco CallManager server.
©2005 Cisco Systems, Inc. All rights reserved. CIPT1 v4.1—1-8
Installation Disks
Disks essential for new Cisco
CallManager 4.1 installation:

Configuration Information
• New installation or server
replacement
• Cisco product key
• Username and
organization name
• Computer name
• Workgroup
• Domain suffix
• TCP/IP properties
• Domain Name System
• SNMP community string
• Database server
• Password for system
administrator

As you perform the Cisco CallManager installation, the automated setup process prompts you for the
information that is necessary to build Windows 2000, Microsoft SQL Server 2000, and Cisco
CallManager with a base configuration. The entire operating system installation process, excluding
preinstallation tasks, takes approximately 25 to 45 minutes per server, depending on your server type.
Installing Cisco CallManager, excluding pre- and postinstallation tasks, takes 45 to 90 minutes per
server, depending on your server type.
The process erases all data on the server hard disk. During the installation, you are prompted for the
following items:
n New installation or server replacement: Choose this option if you are installing the Cisco
IP telephony application for the first time, overwriting an existing installation, or replacing a
server. To replace the server, you must store the data to a network directory or tape device
before the operating system installation. Choosing this setting erases all existing drives.
n Cisco product key: Cisco supplies a product key when you purchase a Cisco IP telephony
product. The product key is based on a file encryption system that allows you to install only

domain name (FQDN) of the Cisco CallManager server. If you do not use DNS, use the
server IP address, instead of a server name, to register the telephones with Cisco
CallManager. Refer to the Cisco CallManager Administration Guide, or the online help in
the Cisco CallManager application, for information about changing the server name.
Note Before you begin installing multiple servers in a cluster, you must have a name resolution
method in place, such as DNS, Windows Internet Naming Service (WINS), or local name
resolution using a configured LMHOSTS file.

If you use DNS, you must verify that the DNS server contains a mapping of the IP address
and the hostname of the server that you are installing. This verification must take place
before you begin the installation.

If you use local name resolution, ensure that the LMHOSTS file is updated on the existing
servers in the cluster before you begin the installation on the new subscriber server. You
must add the same information to the LMHOSTS file on the new server during installation.
n SNMP community string: The Windows 2000 Simple Network Management Protocol
(SNMP) agent provides security through the use of community names and authentication
traps. All SNMP implementations universally accept the default name "public." Cisco sets
the community rights to none for security reasons. If you want to use SNMP with this
server, you must configure it.
n Database server: You must determine whether you will configure this server as a publisher
database server or as a subscriber database server. This selection is permanent. You must
reinstall the Cisco CallManager server if you want to reassign the database server type at a
later date.
Note You must install a Cisco CallManager publisher server before you can install any
subscriber servers.

Note When you are configuring a subscriber database server, ensure that the server that you are
installing can connect to the publisher database server during the installation. This
connection facilitates the copying of the publisher database to the local drive on the

n Default gateway

DNS servers (optional):
n Primary
n Secondary
WINS servers (optional):
n Primary
n Secondary
LMHOSTS file (optional)

Database server (choose one):
n Publisher
n Subscriber
If you are configuring a subscriber
server, supply the username and
password of the publishing database
server:
— Publisher username
— Publisher password

Backup (choose one or both):
n Server
n Target

New Windows 2000 administrator
password Postinstallation Procedures
This topic examines the tasks that Cisco recommends that you perform after installing Cisco

n Smart Card (Cisco CallManager 3.2 and earlier)
n Smart Card Helper (Cisco CallManager 3.2 and earlier)
n Computer browser (Cisco CallManager 3.2 and earlier)
n Distributed File System
n License Logging Service
In addition to the services listed here, you should stop and set the following services to manual on the
subscriber servers: