Prime Collaboration Deployment, Uncategorized, Upgrade CUCM

Upgrade CUCM 8.6 to 11 Using PCD

Performing upgrades and migrations of CUCM has always been a long, manual process that required lots of staging and prepping as well as after-hours work.  With the release of version 10.X Collaboration Suite, a new product called Cisco Prime Collaboration Deployment (PCD) was released.
It allows the user to perform tasks such as migration of older software versions of clusters to new virtual machines, fresh installs, and upgrades on current clusters.In summary automates upgrade and migration task.
Once PCD is installed and configured, it can be used to perform a variety of tasks cutting down on the amount of time and frustration of a large manual migration.

Supported Releases for the Upgrade Task on PCD Version 10.5

These include releases for the upgrade task on the Upgrade Application Server or Install COP files:

  • Cisco Unified CM Releases Supported: 8.6(1-2), 9.0.(1), 9.1(1), 9.1(2), 10.x
  • Cisco Unified Presence (CUP) Releases Supported: 8.6(3), 8.6(4), 8.6(5)
  • Cisco Unified CM – IM and Presence Releases Supported: 9.0(1), 9.1(1), 10.x
  • Cisco Unified Contact Center Express Releases Supported: 9.0(2), 10.x
  • Cisco Unity Connection Releases Supported:
    • From 8.6(x) to 8.6(x)
    • From 8.6(x) to 9.x
    • From 9.x to 9.x
    • From 10.0(1) to 10.x

This document is focused on the upgrade task on PCD Release 10.5.I show in an Earlier post the steps for Installation of PDC https://ccieroot.com/2016/03/23/installation-of-cisco-prime-collaboration-deployment/

I spend the last couple of weeks searching in internet for a way to upgrade from 8.6 to 11 and there was no single resource i could catch to it so i made my OWN

Note.The test been Done on UCSC-C220

So let’s Start
First Download the RSA Keys from Cisco Web Site

RSA keys are used to sign Cisco Unified Communications Manager releases and other updates such as Phone Firmware, Locales, Dialplans, other cop files. This cop can be installed on any UCM or see README for versions needing this cop.
ciscocm.version3-keys.cop.sgn
and put it in your SFTP Folder and Upload to your CUCM 8.6
1
Fill the SFTP Information
2
Choose the RSA Key
3

4

56
Then i will upload the Image to PCD through Filezilla
1
First Create a Site Manager2
Add the IP of your PCD and use Admin username : adminsftp & Password:same one used for web  login in PCD3

4
Press Ok
5
Now you are inside the PCD Directory if you need to upgrade an existing Cluster then copy the ISO to the Upgrade Folder if you want to create a new Cluster then copy the ISO to the Install Folder
In our Case i want to upgrade
1a

Select the ISO Image and Choose Upload4
Now the Upload Start
5
Now it’s Complete and the ISO Available Under your Upgrade Folder on the right and also you can check your Data store in the web page
4.png
Login to the PCD
232425
I can check my ISO Image from Administrator Tab – SFTP Datastore
6
Now To Add a Cluster go to Inventory – Clusters – Discover Cluster1
Fill the Cluster Information2
3
Then Choose to Assign Function to the Server4
Choose the Function that this CUCM is Providing5
Now we add the Cluster Successfully
6
Next Task is to Upgrade
From Task Tab – Upgrade
Then Choose to Add a New Upgrade Task
1
Select from the Drop Down the Cluster and the Product2
Browse From The SFTP The ISO Image
3
If the Image is not Valid or not Supported it will not Show when you select
“Valid Files Only”7Choose to Start Task Manually or Schedule and Choose Automatically Switch to the new Version After Successful upgrade6
you can Also Specify the Sequence 7
Review the Task Steps5.png
The Task been Added Successfully9
Now go to the right and click on Start Task Immediately 10
From Monitoring Tab you Can see your Task  8.png
or Press View Log and see what happening 12
You can Watch the Installation through the CLI Page
the system shutting down
6
Then the Installation Process Start8

9
Now Finally it Finished and it Switched to the New Image 11.0.110.png
And in the monitoring Page it show the task finish successfully on the PCD Page
9.png
Now Login to the Web Page

11.png
and Here the new CUCM Page and it shows the System Version 11.0.1 and you only need to upload the new License
11.png

;D

 

Standard
CUCM, UCCX

MediaSense Call Recording

Call Center Recording helps organization reliably record and evaluate calls for best training and quality assurance.
Media Sense is a Rich software solution for Cisco IP telephony and Contact Center. It’s provide call recording and live monitoring for Active calls

The Installation is basic just like any Cisco product (CUCM, UCCX …etc)
so i will start by the MediaSense Setup wizard and Requirement

First CUCM Part
create an AXL User I name it mediasense
User Management – Application User
1Second Create a record profile I give it Destination address2
and Assign this to the Agent Directory Number Whom you want to Record
7
now back the phone page & enable the Built in Bridge
Built in Bridge

Most Important Step is to Create a Transcoder and Assign it to the Device pool

Then Create a SIP Trunk to the MediaSense Server
our MediaSense IP Address is 172.16.245.244345
Last create a Route Pattern to the 399 and Gateway is the MediaSense Trunk that you created earlier6Now Let’s start from the Media Sense Setup Wizard
1.png

2

3
Enter the IP Address of the CUCM and AXL username and Password
4
Select the CUCM
5

6
Now you finish and login again
7
Make sure to select the servers that would work as AXL and Call Control Service Providers 8
Select the user That would Listen to the recording
9
Choose the Prune policy Configuration
10
Type the Incoming Call rule which is your Destination Address in CUCM 399 and Choose the Action type
11
Most Important is the Archive were you will save your Recording Media12
Now logout and provide your Call Center Supervisor by the link
in our case
https://172.16.245.244:8440/mediasense/login.html

13
Now as you can see a call been recorded between extension 7156 and 306 under Active Call
111.png
Simple and Easy
MediaSense

;D

 

Standard
Upgrade CUCM

Upgrade CUCM 8.6 to CUCM 9

Drive to 9
everyone write about it
This document provides procedures for performing a direct upgrade to Cisco Unified Communications Manager Release 9.1.2 from Releases 8.6.2
i Have the Update ISO and i save it in My File and start my SFTP
UCSInstall_UCOS_UNRST_9.1.2.12900-11.sgn

0.png
you will follow the same step of Updating the Device Package which i show in earlier post https://ccieroot.com/2016/03/10/update-device-package-in-cucm/

1
Fill the Detail of the SFTP
2
Here i Choose the Upgrade Package
Screenshot 2016-03-10 20.54.59
And Now the Downloading StartScreenshot 2016-03-10 20.55.57
After Downloading it will ask to Install and give an option to Switch Direct to 9 and Reboot or not
Screenshot 2016-03-10 21.29.42.png
Now the Installation Start
Screenshot 2016-03-10 21.30.21.pngAfter it finish the system will Reboot and Walla your CUCM Reach the 9  ;DScreenshot 2016-03-10 22.37.06.png

9.1.2.png
9.1.2       ;D

Standard
Device Package

Update Device Package in CUCM

Ever face a Problem with Adding a new Model IP Phone to your Environment such as 8845, 8865 ?
will Luckily Cisco always care about her customer and support them with upgrading their device package always
it’s available in the latest Device Package cmterm-devicepack8.6.2.26169-1.cop.sgn Which can be downloaded from Cisco Software download https://software.cisco.com/download/navigator.html?i=!mmd

I will show you the steps to Upgrade your Device Package
First Turn on your TFTP were you have your Device Package
3
Then Login to your CUCM OS Admin Page
The Choose Software upgrades – Install/Upgrade
1
Then Fill the Detail of the SFTP in CUCM page
2
Press Next and choose the Device Package you want
4
Press Next and the Downloading of the Device package Start5
After the Downloading is done it will ask to Install it
6

7
Now After it Finish you need to Restart the TFTP Service
go to Cisco unified Serviceability – Tools – Control Center  Feature Services and Restart the TFTP Service
in case of a big cluster you  need to add the Device Package to each server and Restart them starting by the Publisher
advice always do this after Duty  ;D

and Finally will find that you can add your new IP Phone Model 8845, 8865
8.png
;D

Standard
Collaboration, ILS, URI

URI Dialing Between Clusters

The last blog was about URI Dialing at the same cluster which an easy step https://ccieroot.com/2014/10/30/uri-dialing/
But when it come between cluster there is another new feature Called ILS “Inter-Cluster Look-up Service”
Inter-Cluster Look-up Service (ILS) is a cluster-wide service in CUCM that when configured on and between CUCM clusters, synchronizes information throughout the “ILS Network”.

So after finishing configure the Basic URI and made Sure it working we start next step by configure the trunk between both publisher

Go to Device – Trunk Add New and choose SIP Trunk and the Device Protocol also SIP and here is the final Look

Screenshot 2014-10-30 17.17.34

 

 

 

Screenshot 2014-10-30 17.18.04

 

 

 

If you want to use ILS to support intercluster URI dialing, check the Exchange Directory URI Catalogs with Remote Clusters check box in the Intercluster Directory URI Configuration window.
go to Call Routing – Intercluster Directory URI – Intercluster Directory URI Configuration and check the box and choose a name

Screenshot 2014-10-30 17.29.13

 

 

 

 

 

Before you start to configure the ILS go to the Enterprise Parameter – Change the name of  Cluster ID From StandAloneCluster to What ever name you wish in out case it’s CCIEROOT

ClusterID

 

 

then go to Advanced feature – ILS Configuration
and make your Publisher as the HUB and configure password and press ok but don’t put IP in the field of Registration Server

Screenshot 2014-10-30 17.33.43

 

 

 

 

 

 

 

in the Other Server you configure it as a spoke and put the IP of the hub in the Registration Server

Screenshot 2014-10-30 17.38.37

 

 

 

 

 

 

Then Configure the Route Pattern by going to Call Routing – SIP Route Pattern
from CCIEROOT To ATS and in ATS sever you configure a SIP Route Pattern From ATS to CCIEROOT were the IPv4 Pattern is to our ILS URI Configuration name which was MOTO.LOC

Screenshot 2014-10-30 17.40.21

 

 

 

 

 

Now you can test the call and it Succeed Between Cluster

 

Standard
URI

URI Dialing

SIP Uniform Resource Identifier (URI) based dialing One of the 9 newest feature for CUCM version 9
This is beyond anything you imagine Finally we will forget about calling each other by extension number and the we will start typing the email ID instead to make a call. Seriously SIP URI can be best compared to an email address such as Aysar.Mohamed@ccieroot.com or Aysar.Mohamed@mynaghi.com.sa . A users can dial the called party via URI if they are using 8961, 9951 or 9971.
make sure you have to upgrade the IP Phone firemware to 9.3.1

A SIP address or SIP URI is a Uniform Resource Identifier written in user@domain.tld format (semantically, much like an e-mail address). It addresses a specific telephone extension. A SIP URI can be automatically imported from LDAP (provided the cluster is integrated with an LDAP server such as a mail or the msRTCSIP-primaryuseraddress attribute.

Configuration Steps:

The user name is case sensitive however host is case insensitive (RFC 3261). This parameter is configurable starting CUCM 9.1 (under Enterprise Parameters – URI lookup policy)

Go to Enterprise Parameter
Screenshot 2014-10-30 13.25.35

 

Then when you import the user from LDAP make sure the URI Map to the appropriate LDAP attribute
Screenshot 2014-10-29 22.43.18

 

 

Now if you go to the End User Configuration you will find the Filed of Directory URI is your Email
Screenshot 2014-10-29 22.46.37

 

 

 

 

 

Now Configure a phone and Add Dn as you normally Do then go back to the end user and associate the Device and select the primary DN which you want to bind the Directory URI to it

Screenshot 2014-10-29 22.48.00

 

Screenshot 2014-10-30 11.53.03

 

Now Check the DN
Screenshot 2014-10-29 22.48.44

 

Its automatically bind to the DN

*The Directory URI is put into an automatically generated partition called “Directory URI”.  If you wanna call other DN with Directory URI configured, make sure your CSS has the partition Directory URI.*
You can try to make a call now.  It only supports on hook dialing for URI dialing, so you press the new call softkey, the press the “A B C” softkey so that you can enter alphanumeric characters.
If you don’t want to call the full directory URI, you want to call without the domain name, make sure you change the following in the Enterprise parameter.

Screenshot 2014-10-29 22.49.59

 

Now let’s Test it by dialing
2014-10-30 12.24.35-2

 

 

 

 

and yes it’s Calling by dialing the email address aysar.mohamed@mynaghi.com.sa not the extension

 

 

 

 

 

 

Standard
Active Directory, CUCM

CUCM integration with Active Directory

When you first finish installing the CUCM the Call Manager use it’s own LDAP Directory of End Users which is nice to use, but in case you work in a company with more than 1000 people it’s insane to add them all. so the preferred way is to integrate CUCM with a corporate LDAP weather it was Linux, OS or Windows. in our case i will show you how to integrate CUCM with Windows Active Directory

from Windows Side all what you need is a user with Administrator Right so you will be able to access the Active Directory

now back to CUCM

first activate the service that help you to Sync Between LDAP and CUCM

1

 

Then Go to Cisco Unified CM Administration > System > LDAP > LDAP System to identify what type of LDAP

2

 

 

 

 

 

 

 

Check the Box to Enable Sync from the LDAP Server

3

 

 

 

 

 

 

Now Go Click on System > LDAP > LDAP Directory and click Add New

in this example the Active Directory is my Domain CCIEROOT.COM
the admin user is : aysar.mohamed@ccieroot.com and i put the password for the authenticate with the LDAP
my LDAP Search Base is where i save the user it could be simple as under users. in my case i sync all the user in my domain

and my LDAP ip address is 192.168.200.1

Untitled

 

 

 

 

 

 

5

 

 

 

 

 

 

6

 

 

 

 

 

Click on System > LDAP > LDAP Authentication. This will authenticate CUCM End Users using Active Directory instead of the embedded CUCM directory.

7

 

 

 

 

 

 

8

 

 

 

 

 

at this point your CUCM is ready to Sync so go back to System > LDAP > LDAP Directory and Perform Full Sync10

 

 

 

After performing the synchronization the users which were created in Active Directory are now appearing in the CUCM End User

12

 

 
Open one of the users

13

 

 

 

 
That is it

Note. for the users that been created on the CUCM before the Sync they will be Disabled. to Solve this issue you need to create users for them in the LDAP Directory and Sync again and they will be hilighted.

Standard