Call Manager 8.0 to 9.1 upgrade

We are currently running Call Manager 8, UCCE 8, and CVP 8. ICM/CTI 8. 
We would like to upgrade Call Manager 8 to 9.1 first before upgrading UCCE, CVP, etc., it could be months before these are upgraded.
Does anyone know or foresee any issues if UCCE, CVP, etc., are not upgraded right away after CM is upgraded?
Any comment is appreciated.  Thanks.

Look at the UCCE compatibility matrix as you need the exact versions to find out whether they will work together, of ir you'll need a single window on which to upgrade all.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

Similar Messages

  • Upgrade Call Manager from 8.6.2 to 10.5

    Hello All,
    We are planning to upgrade a Cisco Call Manager Publisher node from 8.6.2 to 10.5. We want to install a new publisher on a new environment, but we are struggling with some questions.
    If we install the Pub node 10.5 can we migrate the configuration from the 8.6.2 to 10.5? Do we need a special tool for this?
    If above doesn't work, we can still migrate the existing call manager towards the new servers and start the upgrade, the only problem we face there is that we have to change the publisher's IP because we want to use a new ip addressing scheme.
    Kr,
    Yannick Vranckx

    Your best bet is to use the new tool: cisco prime collaboration deployment. This fits perfectly into what you want to do here and can easily help you with all aspect of the migration including the ip address change. You can learn how to use the tool here..
    https://www.youtube.com/watch?v=JzG4kz1_hL4

  • What are the essentials needed before upgrading from call manager 9.1.1 to call manager 9.1.2?

    I recently tried to upgrade my call manager in a lab environment from 9.1.1 to 9.1.2 but failed. The error stated that connection had been lost after 2 hours into it. Connect using CLI. Any help would be greatly appreciated.
    Steve

    You mean via GUI??
    What does the upgrade status via CLI says??

  • Upgrading call manager from version 8 to 9

    Hi All
    Can anyone please tell me the summary steps on what I need to do to go from call manager version 8 to version 9?
    many thanks
    Carl

    The answer to your question, is that they entirely depend on you exact CUCM versions, asking here and just saying "8 "does not work. You will need to do your due diligence, and read:
    A) Upgrade guide for your target version
    B) Release Notes
    C) New and changed doc, if not included in the RNs already
    They will provide you with ALL you need to perform the upgrade, pre-reqs, procedure, and post-upgrade changes to the VM. All the information is available on cisco.com under the CUCM main documentation site.
    Once you've been thru those, you can come back with any further questions.

  • Call Manager Upgrade????

    I am running Call Manager 6.0. I want to upgrade my Call Manager Software to 6.1.4. Do I have to upgrade the Call Manager Using FTP over the network or can I just use the local DVD drive to upgrade it?

    you cannot directly upgrade from 6.0.1 to
    6.1.3 or 6.1.4 - the best option would be to upgrade to 6.1.2 and from there
    to either 6.1.3 or 6.1.4.
    you should be able to do it via sftp

  • Ringtones and background images not available after call manager upgrade

    Hi,
          We have upgraded our call manager from version 8.5 to 10.5.  Once after the upgrade we lost all the Ringtones and background images except the two default ringtone and background images.  we got 8945 sccp phones(running 9-3-1 firmware) and 9951 sip phones(running 9-4-1 firmware).  Both these phones lost these list.  However the ringlist.xml is available in the tftp server with all the ringtones and the phones are pointed to the right tftp servers.  I tried to restart the tftp servers and tried again, however that didn't help.   we are using call manager 10.5 and h323 voice gateway.  Could anyone please help on this.
    Thanks
    Barry

    Hi Tony,
         I can see the ringtone files in the call manager (osadmin>tftp file mgmt), i have also restarted the tftp services, but it didn't help.  I believe you advised to re-upload the ringlist file (Ringlist.xml) and try again. I will try this and update you.  Please let me know if you have any other suggestions.
    Thanks
    Barry

  • Cisco Call Manager Upgrade from Ver 5.1.3 to Ver 8.6

    Hi ,
    My organization have 4 Subscribers and 1 publisher between 4 different sites. version of all call manager are 5.1.3. all are running on HP Proliant server.
    I looking to upgrade to Version 8.6. Do I need to upgrade server hardware as well for upgrading latest version of call manager or I can use my old server ?
    Thanks
    Amit Sharma

    Hi GP,
    Thanks for your reply.
    Please find below the hardware details of my old server. these details I get from Cisco call manager application.
    Hardware Resources
    Hardware platform type    7835H
    The CPU type    Intel(R) Xeon(TM) CPU 3.40GHz
    Memory    2048 Mbytes
    Detailed Report
    Machine_Type = XXXX
    Model_Number =
    Serial_Number = GB8637LRFE     
    Product_Name = ProLiant DL380 G4
    BIOS_Version =
    BIOS_Build_Level = P51
    BIOS_Date = 04/26/2006
    BIOS_Manufacturer = HP
    BIOS_Language =
    Number_Of_Enclosures =
    Enclosure_Type.0 =
    Processor_Slots = 2
    Active_Processors = 1
    Processor_Family.0 = Xeon
    Processor_Speed_MHz.0 = 3400
    Total_Enabled_Memory_Mb = 2048
    ROM_Diagnostics_Build_Level =
    Thanks
    Amit

  • What is the procedure of Call Manager upgrade from version CUCM 7.1 (MCS Server) to version CUCM 10.2 (on UCS server)

    Hi
    What is the procedure of Call Manager upgrade from version CUCM 7.1 (MCS Server)  to version CUCM 10.2 (on UCS server) , please let me know the steps to what would be the backup procedures and upgrades.
    Regards
    Gaurav

    I'd suggest reading this guide to make sure you have prepared your environment to support 10.x first. The link below also contains the upgrade path to 10.0(1).
    One of the ways you can do this is:
    1/ Apply refresh upgrade cop file on all servers in cluster.
    2/ Upgrade the cluster to 8.6(2). Take a backup of the cluster.
    3/ Build a cluster of 8.6(2) servers on VMs, and assign them the same hostnames and IP address as the hardware cluster. (You may need to keep these on a separate network until switching off the hardware machines)
    4/ Restore the backup taken from the hardware cluster on to the VM cluster.
    5/ Upgrade VM cluster to 10.0(1).
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100_chapter_010.html#CUCM_RF_UA60AFAB_00

  • Upgrade Call Manager 6.5

    Hello Team,
    Just to get confirmation about the MCS Servers 7800 Series that is it recommanded to upgrade Call Manager 6.5 which is running
    on MCS 7800 Series Server to Call Manager 9. CM-9 us fully unified.
    Thanks,

    Supported Servers for Releases of Cisco Unified Communications Manager (Including Business Edition 3000/5000/6000 and Session Manager Edition) and Cisco Intercompany Media Engine
    http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
    HTH
    java
    if this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • Upgrade Call Manager

    Hello All,
    our company is planning to upgrade Cisco Call manager 5.0 to version 8. Can you please help me out what the procedure will be. Or also what the steps i need to follow to upgrade from 5 to 8.

    Hi ,
    For upgrading call manager from version 5 to 8 , u need to consider the following steps:
    a. you need to have valid ESW and UCSS contract since this would be a major upgrade.
    b. Check for existing Hardware since DRAM and HDD requirements are  different for version 8.0(3) and above.
    http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
    c. you also need to check the software compatibility matrix.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr1.pdf
    regds,
    aman

  • Call Manager Migration 7.1.5 to 9.1 / Trunking : ICT vs. SIP

    Hello All,
         Currently studying for CCNA Voice and have been asked by my current employer to upgrade CUCM 7.1.5 to 9.1.1. There has been a time frame put on the deployment however I want to dig pretty deep into the deployment to learn as much as possible. I am going to start by configuring a trunk between the 2 call manager clusters. from there I will add users to the new call manager and try to convert slowly to the new call manager instead of one big cutover. I will place a route pattern over the trunk so that cucm 9.1 will route through cucm 7.1 while I slowly convert users to the new system. I will then deploy directory numbers in a Staging partition that is not associated with any CSS. Once I have all users and phones configured on the new 9.1 call manager I want to use the bulk admin tool to change the staging partition to the working internal_PT production partition. The users will be imported from LDAP.  My questions are, does this sound like a feasible plan?  Is there any other difference between a SIP trunk and ICT besides the SIP and H.323 protocol? ( I prefer SIP from what I have read) and will having the same users on both boxes interfere with call processing, if these users and phones are not active yet?

    Just for the record. I found the solution to my problem. Checking more logs I read this:
    The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.
    "/usr/local/cm/script/cm-dbl-ontape_backup-install RU PostInstall 9.1.2.11900-12 7.1.5.30000-1 /usr/local/cm/ /common/component/database /common/log/install/capture.txt " terminated. Exceeded max time (240)
    The system will now halt.
    So I accessed the Dissaster Recovery Section on CUCM and deleted the tape backup device that was configured there. After deleting it the upgrade went well.

  • Do I get full conference call management options on iPhone 6 model A1549 if using it with GSM carriers?

    I have iPhone 6 model A1549, bought from and currently using with Verizon. You all must be aware that we can use the same phone for GSM carriers like at&t as well. Now we all know that some of the features related to conference calling are not available on CDMA carriers, like we cant have more than 2 callers, and we can't manage conference calls by making the conversation with one party private for some time and again switching back to conference mode, disconnecting a particular party instead of having to end the entire call etc. reference link- iPhone: Understanding phone features - Apple Support These features are available on GSM models and carriers, I just wanted to ask if I use a GSM SIM from a GSM carrier on this model, do I get these additional conference call management options or I am restricted to Verizon like experience while being on at&t (and while using the at&t SIM in this model)

    Yes, I am dealing with this right now on at&t with a 6 plus. I've been down the same road as you. I got it to work with a windows phone yesterday but not my 6 plus when I switched back to the iPhone. My wifes 6 works fine. I believe it is an at&t issue and not an 8.3 issue. After dealing through several levels of support at at&t, they are telling me it has to do with their transition to hd voice. Some people are having this issue because they are updating their system and some peoples phone profile, on phones that have hd voice capabilities, are not getting added to their line and call forwarding will not work without it. I have a trouble ticket open to their engineering dept and they promise it will work for me on or before the 24th of april. Engineering has to build my phones profile so call forwarding will work with my iPhone.
    This is frustrating because like you, I need to forward my calls because I have no signal in my office and need to forward to another phone so I can get my calls. If at&t would quit dragging their feet and enable wifi calling, this wouldn't be an issue for me. I would suggest you put more pressure on at&t and escalate this until it gets resolved. Or put your sim in a phone that does not have hd voice capability and see if it works then.
    Good luck. I'm keeping my fingers crossed this will be fixed for me on or before the 24th. We'll see.
    EDIT: I see you did put it in another phone and it worked. That backs up that the issue is at&t and their hd voice upgrades. They had no explanation as to why some work and some don't, but have them make sure a profile for your phone is on the line. If not, they'll need to build one for the phone so that it''l work. At least that's the story for now. Like I said, I'll know more in a day or two.

  • Is it possible to take the CDR data from a v4.2 Call Manager and copy it to a separate server where it would be made available for reporting?

    Is it possible to take the CDR data from a v4.2 Call Manager and copy it to a separate server where it would be made available for reporting? We are not interested in migrating the CDR data to v6 because of the concerns it introduces to the upgrade process. Is it possible to get the raw data and somehow serve it from a different machine? (knowing it would be 'old' data that stops as of a certain date). If so, what would be the complexity involved in doing so?
    It seems like the CDR data lives within MSSQL and the reporting interface is within the web server portion of the Call Manager... that's as far as we've dug so far.

    Hi
    It is absolutely possible to get the data - anyone you have in your org with basic SQL skills can move the data off to a standalone SQL server. This could be done most simply by backing up and restoring the DB using SQL Enterprise Manager.
    Moving the CAR/ART reporting tool would be more difficult... if you do actually use that for reporting (most people find it doesn't do what they need and don't use it for anything but basic troubleshooting, and get a third party package) then the best option may be to keep your publisher (possibly assigning it a new IP) and leave it running for as long as you need reporting.
    You would then need a new server to run your upgraded V6 CCM; you may find you need this anyway.
    Regards
    Aaron
    Please rate helpful posts...

  • Call Manager 9.1 Active Directory Question(s)

    Hello All!
    Firstly let me establish that I am not an administrator of our VoIP system however I do manage the Server side of our network.  We are in the process of planning an Active Directory upgrade and I'm having some difficulty getting a question answered about the requirements for  Call Manager.  We are at version 9.1 of Call Manager currently with our Active Directory version at 2003 R2.  We are planning to upgrade to Active Directory version 2008 R2 (functional level) however we would like to use Server 2012 R2 as the OS for our AD servers.  From a Microsoft standpoint this is a valid solution, it's built into Active Directory that you can run at different "functional levels" of AD on higher server operating systems.  Any Call Manager applications that require a Windows operating system would run on whatever works for that (2003 or 2008 etc).  Can we use Server 2012 R2 as the Domain Controller operating system while running at 2008 R2 functional level for Active Directory and still retain our Cisco support?

    Hi Allen,
    This is from Cisco site (you already may have seen this), though it talk about the directory services but it is specifically mentioned 2008. 2012 may work and specially as you are saying with functional level set to 2008 shouldn't have any issues. But Cisco have not tested that and you may get into support issues (if any).
    Its completely tested and supported with CUCM 10.X
    Version 9:
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_0_1/ccmsys/CUCM_BK_CD2F83FA_00_cucm-system-guide-90/CUCM_BK_CD2F83FA_00_system-guide_chapter_010011.html#CUCM_TK_C4E65231_00
    Configure LDAP directory
    If you want to do so, you can add users from your corporate directory to the Cisco Unified Communications Manager database by synchronizing the user data to the database. Cisco Unified Communications Manager allows synchronization from the following directories to the database:
    Microsoft Active Directory 2000
    Microsoft Active Directory 2003
    Microsoft Active Directory 2008
    Microsoft Active Directory Application Mode 2003
    Microsoft Lightweight Directory Services 2008
    iPlanet Directory Server 5.1
    Sun ONE Directory Server 5.2
    Sun ONE Directory Server 6.x
    OpenLDAP 2.3.39
    OpenLDAP 2.4
    Terry

  • Cisco Call manager migration

    Hello All,
    my company recently acquired a call manager 9.1 with the appropriate new  hardware .We have an  existing one that is going out of life cycle with version 6.1.5 . I need your advice , how is the best way to migrate from 6.1.5 to 9.1 if there is a way at all .I do not want to update the 6.1.5 , i want to migrate all the data to the new machine with 9.1 .I have  search all over the internet  for such topic but i can not find one.
    Your help is much appreciated
    Thank you in advance 

    Hi Kamen
    This has been covered many times in this forum - however to give you a few pointers:
    You cannot automatically migrate a 6.x CUCM config to one of a different version. You can only migrate exactly the same version between different hardware platforms.
    The "normal" mechanism to upgrade from 6.x to 9.x would be to either upgrade your existing server to 9.x, backup using DRS and restore onto the new hardware, or, install 6.x on your new hardware, backup / restore and then upgrade to 9.x
    It is quite possible that your new hardware will not run the latest version - in which case, you can sometimes upgrade to an interim release first - e.g upgrade your current version to 7.1(5), install 7.1(5) on your new hardware and do the backup / restore. Then upgrade your new hardware to 9.x.
    If none of the above is possible, then you can use BAT to export out most of your current config, and then import into the new server. Note that BAT will not export everything (e.g. route patterns) and some things must be done manually. There also used to be issued in using BAT to export some security related parameters (e.g. PINs) and export them into a higher version. Note that this is a VERY time consuming process.
    Hope this helps.
    Barry Hesk
    Intrinsic Network Solutions

Maybe you are looking for