CIPT1 Notes

CUCM Basic Information:

CUCM Began with Windows NT and a Windows structured environment, then progressed to Linux.

In 3.X release of Call Manager Cisco made it so that Call Manager had to be installed only on Cisco MCS Servers. Previously it could be installed on anything.

VMWare is allowed specifically for virtualization of UC. Not a Hyper-V (Yet)

Call Manager is the same thing as Cisco Unified Communications Manager

Run time Data ( Intra Cluster Communication)

Actively runs between CUCM servers

Ex. Phone registration

Ex. Cucm failure results in phone reallocation

Database Data ( Database Replication )

Cucm Database Information replicated between servers

Ex. Phone extension mapping

Ex. Dial Plan changes 

CUCM Functions

Call processing

Signaling and device control

Dial Plan administration

Phone features

CUCM Manager Signaling and Media Paths

SCCP

SIP

RTP - Realtime transfer protocol ( does not go through CUCM)

CUCM Hardware, Software, and Clustering

Complete hardware and software solution ( appliance model)

Factory installed and field configured

Can be installed on cisco mcs 7800 series server platform, cucm blades or on approved third party servers from IBM or HP as well as VMWARE

No customer access to operating system

Only gui and CLI

Third party access via documented API only

Supports Clusters for redundancy

Provides database redundancy by sharing a common database

Provides call-processing redundancy by CUCM groups

Call Clustering includes the following :

The publisher

Total maximum of 20 servers running various services including TFTP, media, resources, conferencing, and call processing

MAXIMUM of 8 nodes can be used for call processing CUCM service

Publisher

Read/Write/Copy

Subscriber

Read Only

MCS 7800 Server Platforms

7816    7835

7825   7845

7828

Minimum CUCM requirements

2ghz processor

2g ram

72gb hard disk

Cisco supports VMWARE on versions 7.1(3) and 8.0 server based on Vmware vSphere 4

CUCM Operating System

Appliance OS based on RedHat Linux

OS updates provided by Cisco

Uneccesarry accounts and services disabled

IBM Informix Dynamic Server as the databade

DHCP Server

Cisco Security Agent

Applications

Emergency Responder( version 2.0 and later)

Unity Connection ( 7.0 and later)

Presence ( 6.0 and later)

CUCM Database

IDM IDS database stores

Static configuration

Servers and enabled services within the cluster

Devices

Users

Services that rely on the publisher

CCM Admin - Provisions everything -

CCM User - Provisions users

BAT   - Provisions everything

TAPS -  Updates device records

AXL - Provision everything

AXIS SOAP - Enables and Disables services

CCM - Insert phone

LDAP Sync - Update end user table

License Audit - update license table

User facing features

Call Forward All

Message Waiting Indicator

Privacy enable/disable

DND enable / disable

Cisco Extension Mobility

Hunt-group logout

Device Mobility

CTI CAPF status for end users and application users

** These features do not rely on publisher

Database Access Control

Database access between members of a cluster is protected

By IP access control (dynamic firewall "iptables"

By security password

Special configuration procedure required to enable database access for subscribers

At publisher using CUCM Administration add subscriber to list of servers before installation of subscriber

Licensing Models are available

Device based

DLU are consumed by devices

Different device types consume different numbers of DLUs

User based licensing

Licensed per user

Publisher is responsible for all licenses and maintaining all the licensing

System > Licensing > License Upload

Have to restart CCM Service after upload

CUCM Clusters

Can use approximately 30,000 IP Phones

80ms round trip delay between clusters

Maximum of 8 call processing servers in a cluster

LDAP

LDAP directories store data that do not change often, such as employee information

Information is stored in the database for instances :

High number of read and search requests

Occasional write and update requests

LDAP directories store all user information in a centralized location / server

LDAP Directory Integration with CUCM

• User lookups
• User authentication
• User provisioning (database sync)

LDAP Support in CUCM

• Microsoft AD version 2000 and higher
• Microsoft AD application mode
• iPlnaet or Sun ONE LDAP servers

• OpenLDAP

Supports two types of integrations

1. LDAP sync

2. LDAP sync and authentication

Can do full synchronizations and incremental synchronizations

When doing an LDAP integration users cannot be deleted or added on CUCM