Tài liệu Cisco IP Telephony - Part 1 doc

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

Trang 1

CIPT1

Cisco IP Telephony Part 1

Volume 1

Version 4.1

Student Guide

CLS Production Services: 08.18.05

Trang 2

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

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,

StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc and/or its affiliates in the United States and certain other countries

All other trademarks mentioned in this document or Website are the property of their respective owners The use of the word partner does not imply a partnership relationship between Cisco and any other company (0501R)

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

Trang 3

Table of Contents

Volume 1

Cisco CallManager Operating System, Database, and Supporting Applications 1-8

Trang 4

Midrange and Upper-End Cisco IP Phones 2-7

Cisco IP Communicator Installation and Configuration Overview 2-59Configuring Cisco CallManager for Cisco IP Communicator 2-60

Trang 5

CIPT1

Course Introduction

Overview

Cisco IP Telephony Part 1 (CIPT1) v4.1 prepares you for installing, configuring, and maintaining a

Cisco IP telephony solution This course focuses primarily on Cisco CallManager, the call routing and signaling component for the Cisco IP telephony solution This course includes lab activities in which you will perform postinstallation tasks and configure Cisco CallManager; configure gateways, gatekeepers, and switches; and build route plans to place intra- and intercluster Cisco IP Phone calls You will also configure telephony class of service (calling restrictions) and numerous user telephone features, services, media resources, and applications

Learner Skills and Knowledge

This subtopic lists the skills and knowledge that learners must possess to benefit fully from the course The subtopic also includes recommended Cisco learning offerings that learners should complete to benefit fully from this course

Trang 6

Learner Skills and Knowledge

Cisco Voice over IP (CVOICE)

Fundamental knowledge of converged

voice and data networks

Ability to configure voice interfaces on

Cisco voice-enabled equipment for

connection to traditional, nonpacketized

telephony equipment and to configure the

call flows for POTS and VoIP dial peers

Building Cisco Multilayer Switched Networks (BCMSN)

Ability to configure and operate Cisco

routers and switches and to enable

Working knowledge of fundamental terms

and concepts of computer networking, to

include LANs, WANs, and IP switching

and routing

Cisco Learning Offering Skill or Knowledge

Trang 7

Course Goal and Objectives

This topic describes the course goal and objectives

“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

deployment model

n Configure Cisco CallManager and the Cisco Catalyst switch to enable on-cluster calls and add users, phones, and Cisco IP Communicator to the Cisco CallManager database using manual configuration, auto-registration, or BAT

n Configure Cisco gateways and intercluster trunks, create hunt groups, and create a route plan in Cisco CallManager to enable calling to remote clusters so that the WAN is not oversubscribed, calls are preserved if the WAN fails, and user calling restrictions are in

place

n Configure Cisco CallManager to enable features and services, including conferencing, music

on hold (MOH), speed dials, Call Park, Call Pickup, Cisco Call Back, Barge, Privacy, Cisco

IP Phone Services, Cisco CallManager Extension Mobility, Cisco CallManager Attendant Console, and Cisco IP Manager Assistant (IPMA) and also use these features on Cisco IP Phones

n Configure Cisco CallManager and the client PC to enable Cisco CallManager Attendant Console and Cisco IPMA

Trang 8

Course Flow

This topic presents the suggested flow of the course materials

Course Flow

Course Introduction Getting Started with Cisco CallManager

Enabling Features and ServicesLunch

Establishing

an On-Cluster Call

Establishing

an Off-Cluster Call

Enabling Features and Services A

Call

Establishing

an Off-Cluster Call

Establishing

an On-Cluster Call

Enabling Features and Services

Configuring Cisco CallManager Applications

Establishing an Off-Cluster Call

The schedule reflects the recommended structure for this course This structure allows enough time for the instructor to present the course information and for you to work through the lab activities The exact timing of the subject materials and labs depends on the pace of your specific class

Trang 9

Additional References

This topic presents the Cisco icons and symbols used in this course, as well as information on where to find additional technical references

Course Icons and Symbols

Relational Database

DSP

Digital Signal Processor

VLAN or Cluster (Color May Vary)

File Server

PC

Fax Printer

Videoconference

Video Camera

Camera PC/Video

Digital Certificate

Cisco Glossary of Terms

For additional information on Cisco terminology, refer to the Cisco Internetworking Terms and

Acronyms glossary of terms at http://www.cisco.com/univercd/cc/td/doc/cisintwk/ita/index.htm

Trang 10

Your Training Curriculum

This topic presents the training curriculum of this course

Cisco Voice Career Certifications

Professional CCIE

Exam

<Insert Career Certification>

IPTT 642-425

QOS 642-642

CIPT 642-444

IP Telephony Troubleshooting (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®, CCIP®, CCVP™, or CCSP™) It provides a gathering place for Cisco certified professionals to share questions, suggestions, and information about Cisco Career Certification programs and other

certification-related topics For more information, visit www.cisco.com/go/certifications

Trang 11

CallManager server installation process

Module Objectives

Upon completing this module, you will be able to deploy a Cisco CallManager server in a cluster using

a supported IP telephony deployment model This ability includes being able to meet these objectives:

n 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

n Determine the optimum Cisco CallManager cluster option and IP telephony deployment model for your enterprise

Trang 12

Lesson 1-1

Introducing Cisco CallManager

Overview

A Cisco IP telephony deployment relies on Cisco CallManager for its call-processing and call-routing functions Understanding the role that Cisco CallManager plays in a converged network from a system, software, and hardware perspective is necessary to successfully install and configure Cisco

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

Trang 13

n Activate Cisco CallManager services

n Identify the supported versions of Cisco CallManager required to upgrade to release 4.1

Trang 14

Cisco AVVID

This topic describes the purpose and key components of each Cisco AVVID layer

TAPI, JTAPI, SMDI Cisco Unity Cisco IPCC

Gateway Router Switch

Infrastructure

Cisco IOS Network Services

IP Phone Cisco IP Communicator PC Video

Client

Directory

Cisco AVVID provides the foundation for converged networks The Cisco AVVID strategy

encompasses voice, video, and data traffic within a single network infrastructure Cisco AVVID equipment is capable of managing all three traffic types and interfacing with all standards-based network protocols in each network class

This figure shows the four standard layers of the Cisco AVVID voice infrastructure model: the

infrastructure layer, which lays the foundation for network components; the call-processing layer, which maintains PBX-like functions; the applications layer, where applications that provide additional network functionality reside; and the client layer, where end-user devices reside The key points about the four standard layers are as follows:

n Infrastructure layer: The infrastructure carries data between all network devices and

applications and consists of routers, switches, and voice gateways

n Call-processing layer: Call processing is physically independent of the infrastructure Thus,

a Cisco CallManager in Chicago can process call control for a bearer channel in Phoenix

n Applications layer: Applications are physically independent of call-processing functions

and the physical voice-processing infrastructure; that is, they may reside anywhere within the network

n Client layer: The client layer brings applications to the user, whether the end device is a

Cisco IP Phone, a PC using a Cisco IP Communicator, or a PC delivering converged messaging

Trang 15

Cisco CallManager Functions

This topic describes the primary Cisco CallManager functions within the Cisco IP telephony solution

Cisco CallManager Functions

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

Trang 16

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

Cisco CallManager Functions (Cont.)

Cisco CallManager

IP Phone

Party A

Skinny Protocol Signaling

Real-Time Transport Protocol (RTP) Media Path

Skinny Protocol Signaling

• Cisco CallManager performs call setup and maintenance tasks

using Skinny.

• IP Phones stream audio using RTP.

IP Phone Party B

Cisco CallManager use the Skinny Client Control Protocol (SCCP, or Skinny) signaling protocol over

IP to communicate with Cisco IP Phones for call setup and maintenance tasks When the call is set up, Cisco IP Phones communicate directly using Real-Time Transport Protocol (RTP) to carry the audio You can better understand how Cisco CallManager performs key functions by tracking a basic IP telephony call

Trang 17

Example: Basic IP Telephony Call

In the figure shown, Party A (left telephone) wants to call Party B (right telephone) Party A picks up the handset and dials the number of Party B In this environment, dialed digits are sent to Cisco CallManager, the call-processing engine Cisco CallManager finds the address and determines where to route the call

Using the Skinny protocol, Cisco CallManager signals the calling party over IP to initiate a ring back, and Party A hears ringing Cisco CallManager also signals the destination phone to initiate ringing When Party B picks up the telephone, the RTP media path opens between the two stations Party A or Party B may now initiate a conversation

The IP Phones require no further communication with Cisco CallManager until either Party A or Party

B invokes a feature, such as call transfer, call conferencing, or call termination

Trang 18

Cisco CallManager Operating System, Database, and Supporting Applications

This topic identifies key software on which Cisco CallManager depends

Operating System, Database, and Applications

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

Trang 19

Cisco CallManager Servers

This topic describes the major features of the supported server hardware platforms for Cisco

CallManager Release 4.1

Cisco 7800 Series MCS

7500 2

2 Nocona Xeon

3400 MHz 2U Rack

Mount MCS 7845-H1

2500 2

1 Nocona Xeon

Mount MCS 7835-H1

1000 1

1 Pentium 4 3400 MHz

1U Rack Mount MCS 7825-H1

7500 2

2 Nocona Xeon

Mount MCS 7845-I1

2500 2

1 Nocona Xeon

Mount MCS 7835-I1

1000 1

1U Rack Mount MCS 7825-I1

300 1

Tower MCS 7815-I1

Max Phones Per Cluster

CPU Max.

CPU Equipped Processor

Space Platform

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:

http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_data_sheet0900aecd801979f0.html

Trang 20

Installation CD-ROMs

This topic identifies the CD-ROMs that you must use to install a Cisco CallManager server

• Cisco CallManager 4.1 Software

Cisco CallManager 4.1 upgrade software can be downloaded from Cisco.com or ordered on DVD/CD (includes Cisco CallManager software only, does not include operating system)

All Cisco MCSs and customer-provided servers that meet approved Cisco configuration standards ship with a blank hard drive When you purchase a Cisco IP telephony application, you use the appropriate disks to install or upgrade the operating system and application:

n Cisco IP Telephony Server Operating System Hardware Detection Disk: Checks the

server and displays an error message if it detects an unsupported server After you boot the server using the Hardware Detection CD-ROM, the automated installation process prompts for the correct CD-ROMs to use

n Cisco IP Telephony Server Operating System Installation and Recovery Disk: Installs

the operating system Use only one of the server-specific Cisco IP Telephony Server Operating System Installation and Recovery disks that come in your software kit During the operating system installation, a prompt instructs you to insert the appropriate disk into the drive

n Cisco CallManager 4.1 Software Disk: This disk installs the Cisco CallManager

application on the server

You may also receive a Cisco IP Telephony Server Operating System Upgrade Disk Use this disk to upgrade the operating system on existing (not new) servers in the cluster You do not need to use this disk if you are performing a new operating system installation

Trang 21

Installation Configuration Data

This topic describes the configuration data that you will need when installing a Cisco CallManager server

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 the components that you have purchased It also prevents you from installing other supplied software for general use The product key consists of alphabetical characters only

n Username and organization name: The system will prompt you for a username and an

organization name to register the software product that you are installing Do not leave the field blank You can enter letters, numbers, hyphens (-), and underscores (_)

Trang 22

n Computer name: The system will prompt you to assign a unique computer name, using 15

characters or fewer, to each Cisco CallManager server The computer name may contain alphabetic and numeric characters, hyphens, and underscores, but it must begin with a letter

of the alphabet Follow your local naming conventions, if possible If you want to change the computer name after the application installation, you must completely reinstall the operating system and the application

n Workgroup: The system will also prompt you for a workgroup name A workgroup consists

of a collection of computers that share the same workgroup name Computers in the same workgroup can more easily communicate with each other across the network Ensure that this entry, which must also be 15 characters or fewer, follows the same naming conventions

as the computer name

n Domain suffix: When prompted, you must enter the Domain Name System (DNS) suffix in

the format “mydomain.com” or “mycompany.mydomain.com.” If you are not using DNS, use a fictitious domain suffix, such as fictitioussite.com

n TCP/IP properties: You must assign an IP address, subnet mask, and default gateway

when installing a Cisco CallManager server You should not change the IP addresses after installation because they are permanent properties

Note It is strongly recommended that you choose static IP information, which ensures that the

Cisco CallManager server obtains a fixed IP address With this selection, Cisco IP Phones can register with Cisco CallManager when the telephones are plugged into the network Using Dynamic Host Configuration Protocol (DHCP) can cause problems, including failure

of the telephony system

n DNS: You must identify a primary DNS server for this optional field By default, the

telephones will attempt to connect to Cisco CallManager using DNS Therefore, you must verify that the DNS server contains a mapping of the IP address and the fully qualified 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

Trang 23

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 subscriber server You must supply the name of the publisher database server and a username and password with administrator access rights on that server The installation will be discontinued if, for any reason, the publisher server cannot be authenticated

n New password for the system administrator: Cisco CallManager Releases 3.0 and later

support password protection A prompt at the end of the installation procedure will ask you

to supply a new password for the system administrator.

Note For Cisco CallManager database replication, you must enter the same replication account

password for the publisher and all of the subscribers in the cluster

Example: Configuration Data Worksheet

This table shows the configuration information that you need to install software on your server You should complete all of the fields in the table, unless otherwise noted You must gather this information for each Cisco CallManager server that you are installing in the cluster Make copies of this table, and record your entries for each server in a separate table You should have the completed tables available when you begin the installation

Trang 24

Configuration Data for Cisco MCS

Current time zone, date, and time

DHCP parameters It is recommended that you program a fixed IP address in

TCP/IP properties for the server instead of using DHCP TCP/IP properties (required if DHCP

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

Trang 25

• During upgrades, password resets to default.

• Change passwords on all servers in a cluster.

Stop unnecessary services:

• Publisher and subscribers:

–DHCP Client, Fax Service, FTP Publishing Service, Smart Card, Smart Card Helper, Computer Browser, Distributed File System, License Logging Service

• Subscribers:

–IIS Admin Service, World Wide Web Publishing Service

• Activate services

• Install backup utility and configure the backup settings

You should perform postinstallation tasks to ensure the optimal operation of Cisco CallManager Perform the following tasks for each server that you have installed:

n Change passwords: During installation, all accounts are set to a default password The

server will prompt you to change the passwords for the Cisco CallManager accounts after installation is complete These passwords must be the same for each of the Cisco

CallManager servers in the cluster

n Stop unnecessary services: The Windows 2000 operating system may have services

running that are not necessary When you stop unnecessary services, you gain additional resources that you can allocate to mission-critical Cisco CallManager processes You should stop all of the following services and set them to manual-start status unless they are

otherwise needed on the system:

n DHCP Client

n Fax service (Cisco CallManager 3.2 and earlier)

n FTP Publishing Service

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:

Trang 26

n Microsoft Internet Information Server (IIS) Admin Service: You can provide an

additional level of security by turning off IIS on Cisco CallManager servers that do not need web access, such as subscriber servers Turning off IIS protects unauthorized users from accessing Cisco CallManager in a distributed architecture

n World Wide Web Publishing Service

Both the FTP Publishing Service and the World Wide Web Publishing Service depend on the IIS Admin Service When the IIS Admin Service stops, the FTP Publishing Service and World Wide Web Publishing Service also stop You must set the FTP Publishing Service and the World Wide Web Publishing Service to manual

To open services, choose Start > Programs > Administrative Tools > Services Right-click each service and choose Properties Then choose the startup type, stop the service, and click Apply

n Activate services: Activate Cisco CallManager services that you want to run on each server

in the cluster

n Install the backup utility: Install Cisco BARS and configure the backup settings that

determine when the Cisco CallManager data is backed up and to what device

Trang 27

Activating Cisco CallManager Services

This topic explains the process of selecting and activating Cisco CallManager services after installation

Cisco CallManager Service Selection

• Cisco CallManager Service

• Cisco TFTP

• Cisco Messaging Interface

• Cisco IP Voice Media Streaming Application

• Cisco CTIManager

• Cisco Telephony Call Dispatcher

• Cisco MOH Audio Translator

• Cisco RIS Data Collector

• Cisco Database Layer Monitor

• Cisco CDR Insert

• Cisco CTL Provider

• Cisco Extended Functions

• Cisco Serviceability Reporter

• Cisco WebDialer

• Cisco IP Manager Assistant

• Cisco Extension Mobility

CallManager Serviceability provides a web-based Service Activation tool that is used to activate or deactivate multiple services and to select default services to activate

It is recommended that you activate only the required components for each server in the cluster Each component that you activate adds to the server load

If you are upgrading Cisco CallManager, the services that you have already started on your system will start after the upgrade

Each service performs specific functions for the IP telephony network Some services may need to run

on a single Cisco CallManager server in a cluster; other services may need to run on all of the Cisco CallManager servers in the cluster

The following information briefly describes each available Cisco CallManager service:

n Cisco CallManager Service: Allows the server to actively participate in telephone

registration, call processing, and other Cisco CallManager functions Cisco CallManager Service is the core service of the Cisco CallManager platform

n Cisco TFTP: Activates a TFTP server on Cisco CallManager The TFTP service delivers

Cisco IP Phone configuration files to IP Phones, along with streamed media files, such as music on hold (MOH) and ring files

n Cisco Messaging Interface: Allows Cisco CallManager to interface with a Simplified

Message Desk Interface (SMDI)-compliant, external voice-mail system

Trang 28

n Cisco IP Voice Media Streaming Application: Allows Cisco CallManager to act as an

Media Termination Point (MTP), a conference bridge, a music on hold (MOH) server, and

an annunciator

n Cisco CTIManager: Allows Cisco CallManager to support computer telephony integration

(CTI) services and provides Telephony Application Programming Interface (TAPI) or Java Telephony Application Programming Interface (JTAPI) client support Cisco CTIManager allows you to use applications such as Cisco IP SoftPhone

n Cisco Telephony Call Dispatcher: Distributes calls to multiple telephone numbers (hunt

groups) Cisco WebAttendant and Auto Attendant require Cisco Telephony Call Dispatcher (TCD)

n Cisco MOH Audio Translator: Allows Cisco CallManager to convert MP3 or WAV audio

files into the MOH format

n Cisco Real-Time Information Server (RIS) Data Collector: Allows Cisco CallManager to

write trace and alarm file information to a database or alert an SNMP server

n Cisco Database Layer Monitor: Monitors aspects of the Microsoft SQL 2000 database, as

well as call detail records (CDRs)

n Cisco CDR Insert: Allows Cisco CallManager to write CDRs to the local database and

replicates CDR files to the Microsoft SQL publisher at a configured interval

n Cisco CTL Provider: Works with the Cisco Certificate Trust List (CTL) client to change

the security mode for the cluster from nonsecure to secure

n Cisco Extended Functions: Provides support for some Cisco CallManager features,

including Cisco Call Back and Quality Report Tool (QRT)

n Cisco Serviceability Reporter: Generates the following daily reports: Device Statistics,

Server Statistics, Service Statistics, Call Activities, and Alert

n Cisco WebDialer: Provides click-to-dial functionality by using a web page or a desktop

application

n Cisco IP Manager Assistant: Allows Cisco CallManager to support the Cisco IP Manager

Assistant (IPMA)

n Cisco CallManager Extension Mobility: Allows Cisco CallManager to support extension

mobility functions for roaming users

n Cisco Certificate Authority Proxy Function: Working in conjunction with the Cisco

Certificate Authority Proxy Function (CAPF) application, the Cisco CAPF service can perform the following tasks, depending on your configuration:

— Issue locally significant certificates to supported Cisco IP Phone models

— Request certificates from third-party certificate authorities on behalf of supported Cisco IP Phone models

— Upgrade existing certificates on the phones

— Retrieve phone certificates for troubleshooting

— Delete locally significant certificates on the phone

Trang 29

Cisco CallManager Service Activation

The Service Activation tool activates services in automatic mode It also checks for service

dependencies based on a single-server configuration When you click the Set Default button, the

Service Activation tool chooses the services that are required to run Cisco CallManager based on a single-server configuration For example, if you choose one service, you will be prompted to choose whether you want all the other services that depend on that service to run Cisco CallManager based on

a single-server configuration

You can activate the Cisco CallManager services in the Service Activation window To activate these services, complete the following steps:

Step 1 Open Internet Explorer, and go to http://<CallManager_IP_Address>/ccmadmin The

<CallManager_IP_Address> is the IP address of the Cisco CallManager server Enter the administrative username and password information

CallManager Serviceability interface appears

shown here appears

Step 4 Click the server that you would like to configure from the Servers column Next, click

the services that you would like to activate, and click the Update button (You will

experience a slight delay.) The Service Activation window will refresh when the process is complete

Caution You should activate the Cisco CallManager services from the Service Activation window If

you manually start the services through the Windows 2000 Services administrative tool, unpredictable results may occur

Trang 30

Upgrading Prior Cisco CallManager Versions

This topic identifies the supported versions of Cisco CallManager required to upgrade to Release 4.1

Upgrading to Cisco CallManager 4.1

4.1

Other upgrades must go through one of

the releases above.

Direct upgrades from:

If your server runs a version of Cisco CallManager Release 3.2 or earlier, you must first upgrade every server in the cluster to the latest version of Cisco CallManager Release 3.3 before you can upgrade to a version of Cisco CallManager Release 4.1

Before you perform any upgrade procedures, it is strongly recommended that you install the latest operating system upgrade and service release, SQL service releases and hotfixes, and Cisco

CallManager service release for the versions that currently run in the cluster Cisco provides the service release and corresponding “readme” documentation on Cisco.com To obtain these documents, go to

http://www.cisco.com/kobayashi/sw-center/sw-voice.shtml

Cisco requires that you install Cisco IP Telephony Server Operating System Version 2000.2.6 (or 2000.2.4 with upgrade to 2000.2.6) before you upgrade to Cisco CallManager Release 4.1

Trang 31

Summary

This topic summarizes the key points discussed in this lesson

Summary

• The Cisco AVVID strategy provides the foundation for converged networks and includes the infrastructure, call-processing, applications, and client layers.

• Cisco CallManager functions include call processing, signaling and device control, dial plan administration, phone feature administration, directory services, and a

Summary (Cont.)

• Installing the operating system and Cisco CallManager IP telephony application for a new installation requires several disks Upgrades can be downloaded from Cisco.com

(with required privileges) or ordered on disks.

• Gather configuration data before installing a Cisco CallManager server

• Postinstallation procedures include changing passwords, stopping unnecessary services, activating services, and backing up the system

• You must activate required services for a new installation If you are upgrading, those services that you have already started on your system will start after the upgrade

• Direct upgrades to Cisco CallManager 4.1 can be made from versions 3.3(4), 3.3(5), 4.0(1), or 4.0(2a).

Trang 32

References

For additional information, refer to these resources:

n Cisco Systems, Inc Cisco CallManager documentation

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/index.htm.

n Cisco Systems, Inc Cisco 7800 Series Media Convergence Servers overview http://www.cisco.com/en/US/partner/products/hw/voiceapp/ps378/index.html

Trang 33

Lesson 1-2

Identifying Cisco CallManager Cluster and Deployment

Options

Overview

To ensure the same service availability that the traditional voice network provides, it is critical to build redundancy and failover capabilities into the IP telephony network design The primary ways to achieve these capabilities are to cluster Cisco CallManager servers and to follow recommended design and deployment practices

This lesson discusses the Microsoft SQL cluster relationship and its impact on the Cisco CallManager cluster and options that are available to enterprises to deploy a highly available IP telephony network

Objectives

Upon completing this lesson, you will be able to determine the optimum Cisco CallManager cluster option and IP telephony deployment model for your enterprise This ability includes being able to meet these objectives:

n Describe how the Microsoft SQL cluster relationship provides publisher database

redundancy and server failover capability

n Describe the two types of communication that are used to ensure database replication and synchronization throughout the cluster

n Describe the advantages and disadvantages of two design schemes that provide

call-processing redundancy within the cluster

n Identify the four supported IP telephony call-processing deployment models

Trang 34

n Identify the major characteristics and design guidelines of a single-site IP telephony deployment model

Trang 35

n Identify the major characteristics and design guidelines of a multiple-site centralized call-processing deployment model

n Identify the major characteristics and design guidelines of a multiple-site distributed cluster call-processing deployment model

n Identify the characteristics, limitations, and advantages of clustering over the IP WAN

Trang 36

Microsoft SQL Cluster Relationship

This topic describes how the Microsoft SQL cluster relationship provides database redundancy and failover capability

Microsoft SQL Cluster Relationship

a database and support a common group of IP devices.

redundancy for the SQL database.

publisher server and up to eight subscriber servers.

publisher replicates to subscribers.

Publisher

Subscriber

Subscriber Subscriber

The voice network is one of the most reliable business networks because PBX vendors design their systems to provide 99.999 percent uptime To provide the same level of voice network reliability for IP telephony service, you must cluster Cisco CallManager servers A Cisco CallManager cluster is two or more servers that share the same database and work together to support a common group of IP

telephony devices

Clustering servers provides two important functions: It eliminates a single-server point of failure and allows multiple devices to work together in one call-processing entity The database replication

capability provided by Microsoft SQL Server makes clustering possible by allowing the same database

to be on multiple machines Database replication makes it appear as if a single machine is handling call processing and other functions and ensures that standby processors can seamlessly step in and fulfill the functions if the primary processor fails

You must have at least two Cisco CallManager servers to obtain this redundancy, and one of these servers must be a publisher database server The publisher database server manages the only writable copy of the Microsoft SQL Server 2000 database The subscriber database servers maintain read-only copies of the database You can have only one publisher server and up to eight subscriber servers per cluster (a Microsoft SQL restriction)

When you make changes to the Cisco CallManager configuration, these changes are written directly to the publisher server The publisher then replicates these changes to the subscriber servers When the publisher server is offline, the Microsoft SQL Server 2000 database automatically locks, and thus prevents further database changes The IP telephony network continues to operate, but you will not be able to add or configure any devices that are managed by Cisco CallManager

Trang 37

When the publisher is down, the subscribers store Call Detail Records (CDRs) until the publisher comes back online, and then the subscribers update the publisher with the CDRs

In Cisco CallManager Release 3.3 and later, a cluster is capable of handling approximately 30,000 Cisco IP Phones This cluster limitation does not restrict the size of the voice over IP (VoIP) network

By creating additional clusters, you can increase the network size Intercluster trunks allow devices to communicate between cluster boundaries

Trang 38

Intracluster Communication

This topic examines the two types of intracluster communication

Intracluster Communication

Intracluster Run-Time Data

Microsoft SQL Database

Publisher

Subscriber Subscriber

n Database replication: During normal operation, all of the Cisco CallManager servers in a

cluster read data from and write data to the publisher database Periodically, the publisher automatically updates the backup copies of the database If the publisher database becomes unavailable, the various Cisco CallManager servers in the cluster continue to operate from their local backup copies of the database All data entry to the publisher database is denied if the link to the publisher, or the publisher itself, is down When the publisher database is restored, normal operations resume

n Run-time data: The second type of intracluster communication is run-time data, which is

used for registration of Cisco IP Phones, gateways, and digital signal processor (DSP) resources Run-time data is shared with all of the members of the cluster and ensures the optimum routing of calls between members of the cluster and the associated gateways When a device (such as a Cisco IP Phone) registers with its primary Cisco CallManager server, the primary updates all of the other Cisco CallManager servers in the cluster After registration, the device sends a TCP keepalive message to the primary server every 30 seconds and sends a TCP connect message to its secondary Cisco CallManager server When the Cisco IP Phone detects the failure of its TCP keepalive message with the primary Cisco CallManager server, the device attempts to register with its secondary Cisco

CallManager server The secondary CallManager server accepts the registration from the device and announces the new registration (through intracluster run-time communication) to all of the Cisco CallManager servers in the cluster The device initiates a TCP keepalive message to the secondary Cisco CallManager server (the new primary of the device) and sends a TCP connect message to a tertiary Cisco CallManager server (the new secondary of the device)

Trang 39

Cluster Redundancy Designs

This topic examines two cluster designs that provide call-processing redundancy

1:1 Redundancy Design

• High availability (upgrade)

• Increased server count

• Simplified configuration

Primary Secondary/

Backup

Publisher and TFTP Server (Not Req <1000)

Publisher and TFTP Server

2500 IP Phones (5000 Device Units)

5000 IP Phones (10,000 Device Units)

10,000 IP Phones (20,000 Device Units)

Primary

1 to 2500 Backup

Backups

1 to 2500

5001 to 7500

2501 to 5000

7501 to 10,000

Cisco MCS 7835 Cisco MCS 7835 Cisco MCS 7835

In a 1:1 Cisco CallManager redundancy deployment design, you can have a dedicated backup server for each primary server This design guarantees that Cisco IP Phone registrations will never overwhelm the backup servers, even if multiple primary servers fail However, the 1:1 redundancy design considerably limits the maximum cluster size and is not cost-effective

Each cluster must also have a designated TFTP server Depending on the number of devices that a server is supporting, you can combine this TFTP server functionality with the publisher or subscriber Cisco CallManager servers, or you can deploy the TFTP functionality on a separate, standalone server The TFTP server is responsible for delivering IP Phone configuration files to each telephone, along with streamed media files, such as music on hold (MOH) and ring files; therefore, the TFTP server can experience a considerable network and processor load

In this example, a Cisco 7835 Media Convergence Server (MCS) is used because each Cisco

CallManager server installed on that platform supports a maximum of 2500 Cisco IP Phones A single Cisco CallManager is the primary server, with a secondary server acting as a dedicated backup The primary or backup server can also serve as the Microsoft SQL publisher and the TFTP server in smaller

IP telephony deployments (fewer than 1000 IP Phones)

When you increase the number of IP Phones, you must increase the number of Cisco CallManager servers that are required to support the telephones Some network engineers may consider the 1:1 redundancy design excessive, because a well-designed network is unlikely to lose more than one primary server at a time With the low possibility of server loss and the increased server cost, many network engineers elect to use a 2:1 redundancy design

Trang 40

2:1 Redundancy Design

• Cost-efficient redundancy

• Service impacted during upgrade

Primary Secondary/

Publisher and TFTP Server

2500 IP Phones

(5000 Device Units)

5000 IP Phones (10,000 Device Units)

10,000 IP Phones (20,000 Device Units)

1 to 2500

5001 to 7500

2501 to 5000

7501 to 10,000

Cisco MCS 7835 Cisco MCS 7835 Cisco MCS 7835

In a 2:1 Cisco CallManager redundancy deployment design, you have a dedicated backup server for every two primary servers Although this design offers some redundancy, there is the risk of

overwhelming the backup server if multiple primary servers fail In addition, upgrading the Cisco CallManager servers can cause a temporary loss of service because you must reboot the Cisco

CallManager servers after the upgrade is complete

Network administrators use this 2:1 redundancy model in most IP telephony deployments because of the reduced server costs If you are using a Cisco MCS 7835 (shown in the figure), that server is equipped with redundant, hot-swappable power supplies and hard drives When you properly connect and configure these servers, it is unlikely that multiple primary servers will fail at the same time, which makes the 2:1 redundancy model a viable option for most businesses

Tiêu đề	Cisco IP Telephony Part 1
Trường học	Cisco Systems, Inc.
Chuyên ngành	Cisco IP Telephony
Thể loại	student guide
Năm xuất bản	2005
Thành phố	San Jose

Định dạng
Số trang	158
Dung lượng	1,41 MB