CCNA Collaboration – Notes, Chapter 13

Cisco Unity Connection, Voice Messaging

Cisco Unity Connection (CUC) is a full featured voice messaging, auto-attendant and voice recognition system. CUC can support 20,000 mailboxes on a single cluster. Built in IMAP server allows email access to voice messages. Data and message store database are local to the server using Informix Database Service application.

CUC is installed as a VM guest on supported hardware. CUC 10.x is linux based OS.

CUC supports integrations with traditional PBX systems that support native IP or digital TDM circuit that can be connected via PBX IP Media Gateway (PIMG) or T1 IP Media Gateway (TIMG).

Users can be added manually, with BAT (CSV, imported from CUCM using Administrative XML Web Service (AXL) or synced directly from LDAP.

CUC integrates with MSoft Exchange using Web-Based Distributed Authoring and Versioning (WebDAV) providing calendar and journal information for integrations with MeetingPlace.

CUC provides traditional Telephone User Interface (TUI) for interaction with DTMF and Voice User Interface (VUI) for handsfree interaction and IP Phone View (Visual Voicemail).

CUC can be setup as redundant active/active pairs


CUCM and CME are supported using SCCP or SIP

Voicemail Port Wizard in CUCM simplifies integration with CUC. The system generates voicemail ports in CUCM and adds them to a Line Group. Admins must manually configure the Hunt List and Hunt Pilot to support the Line Group.

The Hunt Pilot is referenced by the voicemail pilot

SCCP Integration with CUCM

  • Voicemail Profile
  • Voicemail Pilot
  • Hunt Pilot
  • Hunt List
  • Line Group
  • Voicemail Port 1 – X

In SCCP integrations the MWI (Message Waiting Indicator) is a unique DN for on and off. The DN’s must match in CUCM and CUC.

SIP Integration with CUCM

Instead of a Hunt Pilot and Voicemail Pilot, SIP points to a route pattern which points to a SIP trunk.

  • Voicemail Profile
  • Voicemail Pilot
  • Route Pattern
  • SIP Trunk

SIP is able to handle MWI within it’s signaling

CUC Features

General Configuration – System timezone, language, max greeting length


  • Audio Text Admin – Manage call handlers, directory handlers and interview handlers
  • Audit Admin – Enable/disable application and database auditing, config audit settings, view or delete audit logs
  • Greeting Admin 
  • Help Desk admin – Reset user pins, unlock accounts and view user settings
  • Mailbox Access Delegate – Access to all messages, access on behalf of users
  • Remote Admin – Allowed to use remote tools
  • System Admin – Top level admin role
  • Technician – Access to all functions that enable management of CUC and phone system integrations
  • User Admin – Manage user accounts

Enterprise Parameters and Service Parameters

  • LDAP
  • Call Handlers
    • System Call Handlers – Greetings that can be customized to offer user input options and automation for playing different greeting depending on time of day
    • Directory Handler – Search CUC directory for a user they want to contact
    • Interview Handler – Record answers to questions
  • Call Routing
  • Direct Routing Rules
  • Forwarded Routing Rules
  • Distribution Lists
    • Send voice message to a group of users
  • Authentication Rules
  • Dial Plan
    • Concept of partitions and CSS

Users and Mailboxes

User Templates provide a way to create new user accounts. Template settings are applied as users are created. Changing the template does not go back and change existing users.

2 default templates exist: administrators and users

Template Basics:

  • Name – Name of the template
  • Phone – Dial plan, Class of Service and schedule
  • Location – Geographic location, language and timezone

Class of Service (CoS), different than L2 QOS CoS, method of assigning and restricting user privileges. Unlimited CoS’s can be defined

  • Class of Service
    • Timers
      • Recorded Name Length
      • Greeting Length
      • Message Length
    • Features
      • IMAP
      • Unified Personal Communicator
      • Personal Call Transfer Rules
    • Restrictions
      • Distribution Lists
      • Restriction Tables

End Users

New end users require little configuration because of templates. Unique settings: alias, name, mailbox store, extension and alternate extensions

Extension is required – should be primary users DN, it’s the caller ID CUC uses to determine the owner of the mailbox.

WAN Failures – If the users access CUC over the WAN and its down, SRST using AAR can allow calls to CUC to be routed over the PSTN, the users 10 digit PSTN caller ID will not be recognized unless the alternate extension is entered.

Voicemail Box- admin can choose to list a user in the directory, record the voice name and record a greeting

Private Distribution Lists – Each user can create 99 private DLs with a max of 999 members. The DL is only visible to the user that created it and the administrator of CUC.

Notification Devices – Users can be notified of a new message of up to 3 PSTN numbers and email

User Creation

  • Manual
  • BAT
  • Migration from Unity
  • Import from CUCM over AXL
  • LDAP

Voicemail Boxes

Associated with each user. Held in the database and synced between the 2 CUC servers in the active/active redundant pair. Admins can set message aging policies and move read messages to deleted items after a specified number of days (disabled by default). Messages in the deleted folder are deleted after 15 days by default.

Mailbox Size – Default 12MB, prevented from sending new messages at 13MB and cannot send or receive at 14MB.

12MB is approx 200 minutes of G.729 or 25 minute of G.711


CUCM and CUC Integration

Start on CUCM

Don't forget to add an External Number Mask, as I did

Don’t forget to add an External Number Mask, as I did

I ended up going back into the config and deleted 249 voicemail ports to make the config simpler 

Create a new Hunt List

Add Line Group that was created in the Voicemail Integration Wizard to the Hunt List

Add Line Group that was created in the Voicemail Integration Wizard to the Hunt List

Create DN’s for MWI for SCCP integration – Advanced Features > Voice Mail > Message Waiting

Desc was changed to MWI On

Desc was changed to MWI On

Create Voicemail Pilot

CUCM Config is complete for integration. Moving to CUC, services have already been enabled

Clicked on default inside of Phone System, need to add a port group, choose in upper right corner

Clicked on default inside of Phone System, need to add a port group, choose in upper right corner

Add CUCM for AXL service for user data integration – Telephony Integration > Phone System

0 is highest preference 

0 is highest preference 

Edit Port Group servers

Do this if you have subscribers in the environment. My lab does not have any additional servers, so I will skip this step.

Do this if you have subscribers in the environment. My lab does not have any additional servers, so I will skip this step.

Config User Template

Change authentication rules as needed. Web is for Jabber

Change authentication rules as needed. Web is for Jabber

Add a user manually

CCNA Collaboration – Notes, Chapter 12

Enabling Mobility Features in CUCM

Mobility features allow users to interact with devices and applications no matter where they are. The intent is to extend users to use their enterprise phone number for both inbound and outbound calls seamlessly.

Mobile Connect

Mobile connect – Single Number Reach (SNR) allows the enterprise phone number to be a single number that will ring multiple other devices (cell phone, desk phone, etc.) This allows users to give out a single number that can reach the user regardless of location. If a user answers their enterprise phone from their cell phone they can move the call back to their desk phone or vice versa. If the call was answered on the desk phone, the mobility softkey can be pressed and the call seamlessly moved to the cell phone without dropping the call.

Mobile Connect is configured using Remote Destination Profiles to configure a virtual phone that share configuration settings with the users primary IP phone. Up to 10 remote destinations can be configured per user.

Access Lists can be configured (not related to router ACLs) to control which calls ring which rdp and time of day.

Mobile Voice Access (MVA)

MVA provides SNR consistency for outbound calls. Accessing CUCM from a cell the user can instruct CUCM to place a call as if it was from the users IP Phone. Users call into a specific PSTN DID to access the MVA service.

Configuring Mobile Connect (SNR)

  1. Configure softkey template to add Mobility key
  2. Configure user accounts for mobility
  3. Configure phone to support mobility features
  4. Create remote destination profile and assign to user
  5. Add remote destinations to remote destination profile
  6. Configure ring schedules for remote destination
  7. Configure access list and apply to remote destination
  8. Configure service parameters

Under the End User

Under the End User

Configure MVA

  1. Activate MVA service
  2. Configure Service Parameters
  3. Enable MVA for user
  4. Configure MVA media resources
  5. Configure MVA VXML application on Voice Gateway

Output below borrowed from CCNA Collaboration CICD 210-060 Official Certification Guide

! Define the MVA Application and URL
 service mva
dial-peer voice 50001 pots
! Associate the MVA application to this dial peer
 service mva
! Match the PSTN MVA access number to this inbound dial peer
 incoming called-number 4085555000
dial-peer voice 50002 voip
! Match the PSTN MVA access number to this outbound dial peer
 destination-pattern 4085555000
! Identify the CUCM server running the MVA service VXML app referenced above
 session target ipv4:
 dtmf-relay h245-alphanumeric
codec g711ulaw
 no vad

CCNA Collaboration – Notes, Chapter 11

Enabling Telephony Features with CUCM

CUCM Extension Mobility

Allows users to log into any phone in the cluster. Used when users move desk to desk. Users personal configurations such as DN and speed dials follows the user to whatever phone they log into.

EM is an IP Phone service. It applies user specific device profiles to the phone after login. Administrators have 3 options to set system behavior if a user logs into multiple phones concurrently.

  • Allow multiple logins – User can be logged into multiple phones at the same time. Has a shared line effect. All phones will ring when the DN is called
  • Deny Login – Users can only log into one device at a time. Will receive error message, must log out of other phone first
  • Auto Logout – User can only be log into one device at a time. First device will be logged out of after successfully logging into second phone

When no user is logged into the phone a device profile can be applied (logout device profile).

  • MoH
  • Phone button template
  • Softkey template
  • user locale
  • DND
  • Privacy setting
  • Service subscriptions
  • Dialing name

Enabling Extension Mobility

  1. Activate EM service
  2. Configure EM service parameters
  3. Add EM service
  4. Create a default device profile for each phone model
  5. Create device profiles and subscribe to EM server
  6. Create end users and associate with device profile
  7. Enable EM for phones and subscribe phones to EM service

CUCM Telephony Features

Call Coverage – References features and mechanism used to ensure that calls are answered under most circumstances

  • Call Forward
    • Call Forward All (CFA) – Forward all calls to a destination number. Call Forward search space is used. Line and device search space are ignored
    • Call Forward Busy (CFB) Internal / External – When phone is offhook, calls to DN are forwarded to a specific voicemail pilot
    • Call Forward No Answer (CFNA) – Forwarded after Ring No Answer Reversion timer has expired, forward to voicemail pilot
    • Call Forward Unregistered (CFUR) – Used with SRST.
  • Shared Lines – 2 or more phones with the same DN configured on one of the lines. Calling the DN causes both phones to ring. First phone to pick up answers. 2nd phone cannot pickup without Barge feature
    • Barge – Force a 3 way conference with the first phone in a shared line scenario
      • Conference is hosted on the first phone
    • Privacy – Prevent barging into a call
  • Call Pickup
    • DN’s can be assigned to a call pickup group
    • Multiple DNs have the same group number and one of them is ringing another phone can answer by using the Call Pickup softkey
  • Call Hunting
    • Allows a single DN to distribute calls to several phones in sequence
    • Call Hunting Components
      • DN and Voicemail ports – Targets for the call hunting system
      • Line Groups – Assigned to hunt list, can be assigned to one or more hunt lists
      • Hunt Lists – Top/down ordered list of line groups
      • Hunt Pilots – Associated with hunt list. Unique DN, shared line or PSTN number
  • Call Park – Allows users to temporarily attach a call to a call park slot (DN). Any user can pickup a parked call by dialing the park DN.


Allows a button to be configured that calls an intercom line on another phone. The receiving phone auto answers in speakerphone mode with the microphone muted.

Intercom lines cannot call DNs and DNs cannot call intercom lines. They have their own dial plan and permissions (Intercom partition and CSS).


Presence includes instant messaging status’s (online, offline, busy, in a call, etc) or in the phone system, onhook vs offhook.

Presence status can be monitored with the Busy Lamp Field (BLF) speed dial or preence-enabled call and directory lists.

Configuring Shared Lines

Associate a DN to more than 1 device

Associate a DN to more than 1 device

Configuring Barge

Service Paramters, choose the server select Cisco CallManager Service Scroll down to Clusterwide Parameters (Device-Phone)”/> System > Service Paramters, choose the server select Cisco CallManager Service Scroll down to Clusterwide Parameters (Device-Phone)

Scroll down to Clusterwide Parameters (Feature - Join Across Lines and Single Button Barge Feature Set

Scroll down to Clusterwide Parameters (Feature – Join Across Lines and Single Button Barge Feature Set

Configuring Call Pickup

Call Pickup Group”/> Call Routing > Call Pickup Group

Change the softkey layout to allow for Call Pickup Group

Device > Device Settings > Softkey Template

I copied a standard user and created a HELPDESK softkey template, added PickU Up from the left side

I copied a standard user and created a HELPDESK softkey template, added PickU Up from the left side

Add Call Pickup Group to DN

Add Call Pickup Group to DN

Configuring Call Park

Configuring Call Hunting

Pre-req – phones and DN’s already created

Create Line Group – Call Routing > Route/Hunt > Line Group

Create Hunt List – Call Routing > Route/Hunt > Hunt List

Create Hunt Pilot – Call Routing > Route/Hunt > Hunt Pilot

Configuring Intercom Features

  1. Call Routing > Intercom > Intercom Route Partition
  2. Call Routing > Intercom > Intercom Calling Search Space
  3. Call Routing > Intercom > Intercom Directory Number

Change device to add intercom button

Device > Device Settings > Phone Button Template

CCNA Collaboration – Notes, Chapter 10

Understanding CUCM Dial Plan Elements and Interactions

CUCM Call Flows

This chapter reviews:

  • Call signaling and voice traffic flow
  • Components of call routing
  • Call routing decision process
  • Component configuration
  • Redundancy
  • Restrictions

Call Flow – DNS

DNS is not recommended with IP phones

If DNS is used, the phone must complete a DNS name resolution to learn the IP address of CUCM before signaling can occur. This process introduces delay and also reliance on another system (DNS) that could break the call setup process.

After DNS has resolved the name of CUCM to an IP address the call flow is as follows

  1. SCCP or SIP signaling between phone and CUCM
  2. RTP (real-time transport protocol) carries voice phone to phone (CUCM is not in traffic path for voice)

Call Flow – No DNS

Removing DNS reliance (demonstrated in ch9 notes) is recommended in CUCM. This allows phones to use IP to reach CUCM. The call flow becomes simiplified as the DNS step described above is not done and normal traffic flow occurs.

Phones signal to CUCM with SIP or SCCP, CUCM setups call, phones talk directly using RTP

Centralized Remote Branch Call Flow

Centralized deployment – CUCM servers are located at a main location (companies DC) with remote sites connecting over the WAN for both signaling and on-net voice.

Off-net calls could be routed out a local gateway at the site (PSTN or POTs lines installed in voice gateway at the branch)

Signaling remains the same, SCCP or SIP signaling traffic is sent to CUCM, CUCM setups the call between the 2 phones and the voice (RTP) traffic flows directly from phone to phone. The phones can be located in different sites (Branch to Branch, Branch to HQ, etc).

PSTN Backup Call Flow

If WAN fails, phones can no longer register with CUCM and no longer function. In this scenario SRST is recommended to provide local phone registration in the event of a WAN failure.

Survivable Remote Site Telephony (SRST) is a feature that allows branch routers to take over phone registration and call control if phones cannot reach CUCM. SRST provides on-net calling between phones within the branch. If the SRST routers dial plan is configured properly the branch can dial on-net extensions at another site and SRST will modify the dialed digits for PSTN routing.

CUCM will see the phones as unregistered. Reaching the phones over the PSTN is possible if CUCM is setup with an alternate path.

  • Call routing table has 2nd option to provide PSTN gateway and digit manipulation for PSTN dialed digits
  • Call Forward UnRegistered (CFUR) – destination number that calls will be forwarded if the phone is unregistered with CUCM. Used in conjunction with SRST. This is configured for each branch phone to configure the full PSTN number to reach the branch phones

These configurations in CUCM along with the dial plan in SRST will allow the branch site to still be able to call between sites during a WAN failure. When the WAN recovers, phones register back with CUCM and normal call flow resumes.

Centralized Deployment Considerations

CUCM v10 supports a max of 2000 locations and a max of 2100 H.323 or MGCP gateways per cluster.

• H.323 – Protocol created by ITU-T to allow multimedia communication over network-based environments

• MGCP – Media Gateway Control Protocol – Voice signaling protocol created by IETF. Allows voice gateways to be controlled by a centralized call agent (client / server)

There is no limit of number of phones at a branch site, however the number of phones supported by SRST is limited based on the router hardware at the branch site.

WAN’s must be configured with QOS and allocate bandwidth in the priority queue for voice traffic based on the number of concurrent calls that will happen at the site.

Call Admission Control (CAC)

A technique for monitoring the total remaining bandwidth available for voice traffic over a WAN circuit. The purpose of CAC is to prevent voice traffic in excess of what the circuit can support without overflowing the QOS priority queue and causing voice traffic to be dropped. CAC can be implemented using Locations in CUCM (shown in last chapter). RSVP (Resource Reservation Protocol) can also be used, a QOS mechanism.

Locations – track how many calls are between given locations and subtract bandwidth for each concurrent call. If no bandwidth is available, the call is dropped (default CAC behavior). The user gets a reorder tone.

AAR – Automated Alternate Routing – allows calls that would be dropped by CAC to be rerouted over the PSTN. AAR is triggered by CAC when CAC prevents a call over the WAN. AAR requires digit manipulation to retry the call over the PSTN

Distributed Call Flow

Distributed deployments of CUCM, one CUCM cluster signals another CUCM cluster over the WAN. Signaling flows from calling phone to local CUCM and from local CUCM to remote CUCM over the WAN. RTP traffic is setup directly phone to phone across the WAN.

CUCM used the following signaling protocols between CUCM clusters

  • ICT – Inter-Cluster Trunk
  • H.323
  • SIP

CUCM Call Routing – Sources

  • Phone – places a routing request through a dialed number
  • Trunk – Signals inbound calls from another CUCM, CME or call agent
  • Gateway – Signals inbound calls from SPTN to another call agent
  • Translation Pattern – Matches originally dialed digits and transforms them into a new dial string
  • Voicemail Port – Can be source of a call routing request if the application attempts to call, transfer or message notification on behalf of a users mailbox

CUCM Call Routing – Destinations

  • Directory Number (DN) – Unique on-net extension that can be assigned to a button on an IP phone
  • Translation Pattern – Matches a dialed string and transforms them into a new dialed string. This new string is analyzed and routed to a different target
  • Route Pattern – Matches a set of dialed digits and triggers a call routing process that can include one or more potential paths. Hierarchical set of call routing options
  • Hunt Pilot – Specific pattern of digits that can trigger a customizable call coverage system
  • Call Park Number – A pattern or range or patterns that CUCM can use to temporarily hold a call until a user dials the call park number to pick up the call
  • Meet-Me Number – Conference call initiator dials into a Meet-Me number to begin a conference

All destinations are a string of digits or a SIP URI (Uniform Resource Identifier) 

SIP URI – alphanumeric string –

Call Routing Configuration

Components of CUCM call routing: route patterns, route lists, route groups, gateways/trunks

Route Pattern

  • Matches a string of dialed digits
  • Pattern may be specific matching a single dialable number or general and match hundreds/thousands or possible numbers
    • Wildcards are used in the pattern
  • Required to provide PSTN access
  • Can be used to integrate with existing PBX dial plans
  • Associated with a route list or gateway
    • If the route pattern is directly associated with a gateway, the gateway can no longer be referenced by a route group. Gateway is locked to the specific route pattern

Route List

  • Ordered list of route groups
  • First entry is the preferred call routing path
    • If unavailable the 2nd in list will be used
    • Each new call uses the top-down order
  • This allows admins to choose which circuits get used for which type of calls

Route Group

  • List of gateways or trunks that are configured to support circuits to PSTN or remote CUCM clusters
  • Commonly configured to contain devices with similar signaling characteristics 
  • Distribution of the calls is configurable: top/down, circular

Gateways and Trunks

  • Physically terminate and support circuits to PSTN, digital/analog PBX and WAN circuits to remote clusters or IP-TSP circuits to service provider
  • CUCM supports peer to peer gateway protocols – H.323 and SIP
  • CUCM supports gateway control protocols – MGCP and SCCP

Call Routing Behavior

Dial analysis is performed by CUCM by matching dialed digits.

  • SCCP – Digits are collected digit by digit
  • SIP – Keypad Markup Language (KPML) and en-bloc (all at once as a set of digits)

Digit Analysis

CUCM selects a destination for the call routing request based on closest match

T.302 – Wait time, inter-digit timeout – default is 15 seconds. To wait for any additional digits to be dialed. After the timer is finished the call is routed.

Digit by digit analysis means CUCM collects digits one at a time as they are dialed. When collected patterns that no longer match as discarded as routing targets.

Hunt Groups

A hunt group is a set of phones (DN’s) that are reachable by calling a common number.

  • Line Group – contains DN’s that will ring sequentially. Allows for call distribution: top/down, circular, longest idle, broadcast
  • Hunt List – Contains top/down ordered list of line groups. Each call is routed to the first line in the list unless it is busy then the 2nd line will be rung. If the group is busy the next group in the hunt list will be used
  • Hunt Pilot – Matches a dialed string and targets a hunt list (call routing entry). Hunt pilot numbers can be on-net, E.164 or any format required.

Class of Control

Class of Control defines the ability to apply calling restrictions to a device. Configured using partitions and calling search spaces (CSS).

  • Prevent a phone from calling long distance
  • Routing the same called number to different targets depending on the time of day
  • Routing the same called number to different targets at different locations


Grouping of things with similar reachability characteristics. Assigned to things that get dialed.

By Default – one partition exists, null partition

75 additional partitions can be created

  • DN
  • Route Pattern
  • Translation Pattern
  • Voicemail Ports
  • Meet-Me Conference

Calling Search Space (CSS)

Top/down ordered list of partitions. Can be applied to device (phone or gateway) or to line on the phone

One CSS exists by default, contains null partition.

CSS’s are applied to things that make calls

Partitions and CSS

If the target dialed number does not exist in one of the partitions in the CSS, the call will fail

When a route pattern is moved from default partition, it is no longer available to the default CSS

Every CSS includes the default partition and the end of the list.

If both device and line CSS are applied, the partitions in both CSS are concatenated in sequential top/down order. The LINE CSS partitions are listed first followed by the device CSS partitions.

Line CSS overrides the device CSS

Best practice – Setup device CSS to allow full calling privilege to all patterns based on the devices location. The calling restrictions are applied using the line CSS which contain route patterns that match long distance but configured to block the call

CCNA Collaboration – Notes, Chapter 9

Implementing Phones in CUCM

Tasks behind implementing phones into CUCM

Services and Protocols to support IP Phones

  • NTP – Network Time Protocol
    • Standard for providing network based time synchronization
    • Convenience and consistency of the same time on all devices
    • Timestamp for CDR and CMR
    • Some features rely on time (calendar)
    • NTP can be implemented on a core switch or router in the network – configuration examples were done in previous notes
    • During CUCM install NTP is required to be entered before moving forward.
      • Subscriber servers sync their clocks to the Publisher server and IP Phones (SCCP) get their time from the subscriber. SIP based phones need an NTP reference
  • CDP – Cisco Discovery Protocol
    • Layer 2 protocol – mapping information of the network
    • Phones generate CDP messages to learn voice vlan ID
  • DHCP – Dynamic Host Configuration Protocol
    • Allows phones to get IP addresses dynamically
    • IP Address, subnet mask, default gateway, DNS, TFTP (option 150)
    • Router example was done in previous notes
    • I’ll show DHCP being hosted from CUCM later
  • PoE – Power Over Ethernet
    • Described in earlier notes
  • TFTP – Trivial File Transfer Protocol
    • Phones user TFTP to download their configuration files, firmware and other data
    • Required for phones to function properly
  • DNS – Domain Name System
    • Hostname to IP address resolution
    • DNS server must be external to CUCM cluster
    • Asked for during CUCM installation
    • Not required for phones to function, if DNS reliance is disabled (example to follow later)
    • DNS is not hosted by CUCM

IP Phone Registration

  1. Phone gets power – POE or power adapter
  2. Phone loads locally stored firmware imsage
  3. Phone learns voice vlan through CDP
  4. Phone uses DHCP to learn ip information
  5. Phone contacts TFTP server and requests configuration file
    1. Each phone has a customized config file – SEP<mac address>.cnf.xml
  6. Phone registered with primary CUCM server in the config file
    1. CUCM sends softkey template to phones using SCCP

SIP Phone Registration

  1. Same steps 1 – 4 as above
  2. Phone contacts TFTP and request Certificate Trust List File (only if cluster is secured)
  3. Phone contacts TFTP server and requests config file – SEP<mac address>.cnf.xml
  4. Phone downloads SIP dial Rules
  5. Phone registers with primary CUCM in the config file
  6. Phone downloads localization files from TFTP
  7. Phone downloads softkey configuation
  8. Phone downloads custom ringtones

Prepare CUCM to Support Phones

Service Activation

Service Activation This takes a little time to activate the services”/> Go into Unified Serviceability Tools > Service Activation This takes a little time to activate the services

Configure and Verify Network Services

  • NTP
  • DHCP
  • TFTP

DHCP Server Configuration on CUCM

First start with defining DHCP server parameters. The DHCP service on CUCM is only meant to host IP Phones. It is limited to 1000 phones.

Only one DHCP server is supported per cluster. Multiple scopes can be configured on the server

Now that the server is define, we need to add subnets for the hosts

Configure Enterprise Parameters

Cluster wide default settings

  • Device Pool – common configurations to a group of devices. Template to apply several different settings all at once 
  • Cisco Unified CM Group – Top/down ordered list of redundant call processing servers that phones can register to. The list can include a max of 3 servers plus an option SRST reference. Servers can be listed in one or more CM groups
  • Region – Virtual assignment to allow for control of bit rates of calls. Influence the codec used between locations
  • Location – Defines the max bandwidth to be used for concurrent number of calls. If there is not enough bandwidth to add another call, the call is either dropped or rerouted over PSTN if AAR is configured.
    • This is one mechanism of CAC – Call Access Control
  • Date/Time Group – Allows to display the time and date in a desired format. Have the correct timezone show up for sites across the globe
  • Phone NTP reference – SIP phones require an NTP server
  • Device Defaults – Lists all supported devices, firmware, device pool and phone button template each endpoint uses by default
  • Softkey Template – Controls what softkey button functions are available to users
    • Default template provides 2 lines and as many speed dials that are remaining buttons on the phone model
  • Phone Button Template
  • SIP Profile – Allow for one time configuration of repetitive tasks
  • Phone Security Profile – Default is security disabled. Can change to configure the device as secured, encrypt TFTP and modify certificate authority proxy
  • Common Phone Profile – Common phone profile settings

Configuration of these settings is shown below

Adding Phones in CUCM

Phones can be added to CUCM multiple ways

  • Manual Configuration – Config shown below
  • Auto Registration – Phones dynamically add self to CUCMn
  • Bulk Administration Tool (BAT) – Template (CSV) that can be filled out and used to upload phone information
  • Auto Registration Phone Tool (TAPS) – Uses IVR (Interactive Voice Response) to enhance auto registration and BAT
  • Self Provisioning – 

Manually Adding Phone

Add New, choose the phone model type, choose the protocol to register with (SIP or SCCP)

Added a DN to Line1

Added a DN to Line1

Created an End User and associated with the phone and added to Access Groups: Standard CCM User and Standard CTI User

End User and Application Users

Adding a end user was shown above.

End users

  • Associated with an actual person
  • Individual use
  • Assign users features for administrative rights
  • Included in the user directory
  • Can be synced with LDAP

End users can be added using the following:

  • Manual Entry
  • Bulk Import with BAT
  • LDAP Sync

Application User

  • Associated with an application
  • no interactive logins
  • For application authorization
  • Not in user directory
  • Locally provisioned 

Disable DNS Reliance

I did this task before creating the blog. Screenshots below are after changing hostname to IP address.

Disable DNS reliance means that phones will rely on using IP addresses to reach CUCM instead of trying to do DNS resolution.

Servers”/> System>Servers

Change hostname to IP address

Change hostname to IP address

Next go to System>Enterprise Parameters, scroll down and change the hostname to IP address in the URL

CUCM Configuration

Cisco Unified CM Group

NTP Reference

Date/Time Group


Changed default name to HQ

Changed default name to HQ

Added Branch1

Added Branch1

Setup codecs to be used between HQ to Branch1

Setup codecs to be used between HQ to Branch1

Added Branch2 and choose codecs to use between Branch1 and HQ

Added Branch2 and choose codecs to use between Branch1 and HQ


Changed Hub_None to HQ

Changed Hub_None to HQ

Added Branch1 and 2, set audio bandwidth amount between the locations

Added Branch1 and 2, set audio bandwidth amount between the locations

Device Pool


Calling Search Space

CCNA Collaboration – Notes, Chapter 8

Administrator and End-User Interfaces

Chapter 8 goes over the administrator interfaces for CUCM, CUC, CM-IMP and End-Users in CUCM

CUCM Administration Interfaces

CUCM can be accessed via HTTPS or SSH. There are 7 separate interface

  1. CUCM Administration – ccmadmin
  2. Unified Serviceability – ccmservice
  3. Disaster Recovery System – drf
  4. Unified OS Administration – cmplatform
  5. Unified Reporting – cucreports
  6. Unified IM and Presence Reporting – cucreports
  7. CLI

Username and passwords are defined during the installation of CUCM. I do not have pictures of this as I built the VM before I was thinking about doing a blog.

CUCM Administration Interface

Comment: Please Ignore the angry messages in the screenshot. I did not put a license of my server yet and don’t have a DNS server setup in my lab

CUCM admin interface has 9 menus

  • System – Configuration of CM groups, presence, mobility, locations, device pools, regions, service parameters, etc.
  • Call Routing – Define call routing system, call hunting, class of control, intercom, call park, etc
  • Media Resources – MOH, media termination, transcoders
  • Advanced Features – Voicemail integration, inter-company media, extension mobility, etc
  • Device – Gateways, gatekeepers, trunks, phones, remote destinations, etc
  • Application – CUCM Assistant Config wizard
  • User Management – Application users, end users, access control groups and roles
  • Bulk Administration – Perform repetitive configuration tasks in an automated way
  • Help – Searchable help rules

Serviceability Administration

6 menu options

  • Alarm – Configure alarms to monitor for system performance and health
  • Trace – Troubleshooting settings
  • Tools – Turn on/off services
    • Under service activation is where you can turn on CUCM features
  • SNMP – Configure SNMP serttings
    CallHome – Talk back to TAC
  • Help – Searchable help content

I activated most of the services for the lab. I'm only going to have a publisher in my lab so I activated things that may normally not be on in a real world environment

I activated most of the services for the lab. I’m only going to have a publisher in my lab so I activated things that may normally not be on in a real world environment

OS Administration

Allows admins to monitor and interact with the linux based OS

 Monitor hardware-resource utilization (CPU, disk space)  Check and upgrade software versions  Verify and change IP address information  Manage Network Time Protocol (NTP) server IP addresses  Manage server security including IPsec and digital certificates  Create a TAC remote assistance account  Ping other IP devices

 Monitor hardware-resource utilization (CPU, disk space)  Check and upgrade software versions  Verify and change IP address information  Manage Network Time Protocol (NTP) server IP addresses  Manage server security including IPsec and digital certificates  Create a TAC remote assistance account  Ping other IP devices

Disaster Recovery

Provides backup and restore capabilities

Backups can be set on a schedule. Backups must be written to a SFTP server on the network

Unified Reporting

Provides access to system reports. The reports gather information from existing logs and format the data into one-click reports. Data is collected across the entire cluster (publishers and subscribers).


Accessed using SSH. Allows for some of the following

  •  Shut down or restart the system

  • Change versions after an upgrade

  •  Start, stop, and restart service

  •  Modify network settings (IP address, mask, gateway, and so on)

  •  Use network tools such as ping, traceroute, and packet capture

  •  Use the DRS

  •  Add and modify Platform Administration accounts

  •  Display server load and process information

  •  Check server status, including software versions, CPU, memory and disk utilization, hardware platform, serial numbers, etc

CUCM Roles and Access

  • Users are assigned to access control groups
  • Access control groups are assigned to roles
  • Roles define privileges to resources in the CUCM applications
    • Resources – admin web page, reporting tool, feature section
    • Privledges
      • No Access – Deny access
      • Read – Display but cannot edit
      • Update – Full access to edit, modify, delete, update

CUCM has 46 default roles in version 10.6

CUCM has 28 default access control groups in version 10.6

  • Access control groups associate 1 or more roles that provide various levels of access to applications in CUCM. Users inherit privileges based on the role they are a member of. If a user is a part of a multiple roles that have conflicting access levels, the default setting is maximum privileges. This parameter can be modified under enterprise parameters.

Unity Connection Administration Interface

CUC has 6 administration interfaces

  • Administration – cucadmin
  • Unified Serviceability – ccmservice
  • Unity Connection Serviceability – cuservice
  • OS Administration – cmplatform
  • Disaster Recovery – drf
  • CLI

Unity Connection Administration

Menu driven items

  • Users – Provides access to local user database to create / edit users
  • Class of Service – Defines features available to users
  • Templates – Provides a way to define common settings for users
  • Contacts – System Contact: Account that provides interactions with CUC without a mailbox
  • Distribution List – Allow a message to be delivered to multiple users
  • Call Management – Defines call handlers
    • 3 types of call handlers
      • System – Foundational structure of CUC: answer calls, play greeting, route calls, take message
      • Specialized – Directory handler
      • Interview – Interact with a caller using a recorded series of questions
  • Message Store – Mailbox quotas
  • Networking – Configure multple CUC for either digital networking or VPIM environment
  • Dial Plan – Create partitions and calling search spaces
  • System Settings – Global configuration settings
  • Licenses – Licenses available on the system
  • Holiday Schedule – 3 system schedules – All hours, weekdays, voice recognition update schedule
  • External Services – Calendar and Contact information held in Exchange
  • LDAP – Configuration for LDAP synchronization
  • SMTP – Notify users of new messages via email
  • Advanced – Configure advanced settings such as Short Message Peer to Peer
  • Telephony Integrations – Lists and configures phone systems CUC is integration with
  • Tools – Bulk admin and task management

Servicability is similar to CUCM

CM IM and Presence Administration Interface

CM-IMP provides 7 administration interfaces

  • CM-IMP Administration – cupadmin
  • IM and Presence Serviceability – ccmservice
  • IMP OS Admin – cmplatform
  • Disaster Recovery – drf
  • IMP Reporting – cucreports
  • Unified Reporting – cucreports
  • CLI

CM-IMP Administration

  • System – Config for CUCM, inbound / outbound access control lists, licensing and management
  • Presence – Define gateways for providing presence information from CUCM or calendar integrations
    • SIP or Exchange Messaging and Presence (XMPP)
    • SIP for Office Communication, XMPP for Google Talk
  • Messaging – External database for persistent messaging – PostgreSQL
  • Application – Desk phone control, and IP Phone messenger configured here
  • Bulk Administration – Similar to CUCM and CUC
  • Diagnositcs – System status and troubleshooting tools
  • Help – Help contents

CM-IMP Serviceability

  • Alarms and event monitoring
  • Access to trace logs
  • Monitor real-time behavior
  • Feature activation
  • Reports
  • SNMP configuration
  • Monitor disk usage

CUCM End User Interface

Allows users to manage the phone they are associated with. User must be part of the Standard CCM End User role.

Tasks that can be done

  • CHange their password or PIN
  • Add / remove / edit speed dials
  • Download user guide
  • Access the directory
  • Subscribe or unsubscribe from phone services

Home Lab Server

One of my friends at work was able to get his hands on a few servers and was generous enough to give me one for my home lab. It’s a Cisco UCS C22 server that I am running ESXi 6.5.0 on. My plan is to eventually add more memory to thus, unless I can get my hands on a C220 server.

I’m not familiar with VMware at all, so this was a learning experience for me to get up an running. I was able to create a bootable USB drive off my mac with the ESXi hypervisor on it and was able to install that as the hypervisor. I installed VMware because it was free on their site and has the most support around for running different virtual instances.

I don’t have any screenshots of video of the install because it was done before I thought about creating a blog

I have a few servers setup that I go through. The ones in most use are VIRL, CUCM and CUC. I turn on/off the servers as I need them for various lab purposes, either personal or for work. 

I currently use onboard storage and do raid 0 if I remember correctly. If they fail they fail 🙂 

For networking it’s a simple flat network. I’ll eventually get into a more sophisticated setup, but for my use now, ease if the name of the game.


If you’d like to see more or get some more details. Drop a comment below