Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Upgrading from CCM 4 to CCM 5 - license file


Sorry to post this same question again for the third time (I keep re-wording it to try and make sure that I am being understood).

I have upgraded from 3.3 to 4.1 and then to 5.0

I have run DMA and SFTP the file to my nice new CCM 5.0 server and have that running OK now. What I do not have yet are any licenses. I have read and been told that the upgrade process creates an intemediary .xml file that I can use to get a license. The thing that I cannot see is how this is created, where it gets put and what the full filename is.

The DMA process creates 2 files that I can see - and .inf file containing a little basic information such as hostname and network info, DMA also creates a .tar file which is an archive containing 836 files (in my case) which looks like the database information.

What I have NOT found yet is a .XML file that looks anything remotely like a file that says IAmaLicenseInfoFile.xml

I have read the various upgrade and license docos such as :-




None of these seem to say where this vital xml file gets put. Has anyone out there actually managed to do this??

Thanks in advance



Re: Upgrading from CCM 4 to CCM 5 - license file

Cisco CallManager 5.0(1) uses a different installation framework than previous releases. The installation process allows you to perform a basic installation, upgrade from Cisco CallManager 4.x to Cisco CallManager 5.0, and upgrade to a newer service release during the installation.

This URL should help you:

Re: Upgrading from CCM 4 to CCM 5 - license file


Like i said earlier in a different post, the dma file doesnt contain the xml file (atleast visible info). During the upgrade to 5.0 using windows upgrade option, the CM 5.0 wizard imports the information from the dma file stored in a remote ftp server. Once the upgrade is complete, you can go to license unit report and download the temporary license. This content of this file can be emailed to licensing team along with the mac-address to generate the actual license files.

New Member

Re: Upgrading from CCM 4 to CCM 5 - license file

I am looking for the same xml file. Did you ever find it?

Hall of Fame Super Red

Re: Upgrading from CCM 4 to CCM 5 - license file

Hi Frank,

Did you go through this process?

Use the following procedure to register existing licenses and request for new licenses.


Step 1 In Cisco Unified CallManager Administration, choose System > Licensing > License File Upload. ***(On the new 5.x or 6.x build)

The License File Upload window displays.

Step 2 Click View File. A pop-up window displays that has the license information for existing phones and nodes. Copy this information. To copy the contents on this windrow, you can use Ctrl-A (Select All) and Ctrl-C (Copy).

Step 3 On the License Registration window of CCO website, in the text box provided, paste the file contents using Ctrl-V.

Step 4 You must enter the MAC address of the Cisco Unified CallManager server that you are requesting the licenses for, and a valid E-mail Id.

Step 5 To obtain the actual license file, click Submit. A license file is generated.

Step 6 You must upload the license file to the server with the matching MAC address that you provided in Step 4.

During the time you have to wait for the new License from Cisco (not long, usually a couple of hours via email) the phones etc will still work you just can't do any changes of additions to them.

Hope this helps!


Re: Upgrading from CCM 4 to CCM 5 - license file

Can you help me if Cisco CallManager 4.2 can be installed on servers other than Cisco 7800 series,and what is the details of the server specs that make the callmanager work.

New Member

Re: Upgrading from CCM 4 to CCM 5 - license file

I've got it now. For some reason I was under the impression that the DMA tool was going to generate the file.