We are running 2000.2.5 SR5. Cisco recommends downloading the 2.6 exe, copying it to the server and upgrading, but we are not confident about doing this. We want to know why this is not working.

I too am having the same problem. I have a new MCS 7825I which is the fourth server for this customer all bought at the same time. THis server will be used for IPCC but when I use the OS detection that shipped with IPCC it gives this error.

According to the following upgrade guide for 3.3(5), the required OS is 2000.2.7sr1. You will need to upgrade the OS before the CCM upgrade can be performed.

http://ftp-sj.cisco.com/cisco/voice/callmgr/3.3/ciscocm-ffu.3-3-5-ReadMeFirst.pdf

Hope this helps. If so, please rate the post.

Thanks,

Brandon

sorry it does not help my situation at all. My server is new out of the box and has never had any application on it. I am wanting to do a clean install of 2.7 using the cd's that came with IPCC or they cd's that came with call manager and I am having the same problem.

Take a look at the following document for hardware requirements as well as instructions for installing the OS. One workaround the document mentions is to install the 2000.2.4 OS and then upgrade to the latest SR if your hardware is not supported by 2000.2.7.

http://www.cisco.com/univercd/cc/td/doc/product/voice/iptel_os/install/os200027.htm

Hope this helps.

Brandon

I belive this will resolve my issue but I can not find a place do downlad the new OS build for a new server only service releases. I purchased a new server but they sent me the old software. does anyone know how I can get it?

Okay, here's what TAC told me. Start here: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm#OS_servers

Basically it tells you 2.7 is the only compatible OS. Download here:

http://www.cisco.com/cgi-bin/tablebuild.pl/cmva-3des

If you need a bootable 2.7a disk open a TAC case and see if they will RMA you a copy (you will need your Cisco Account Manager's help)

I have a personal issue with this becasue the CallManager upgrade docuementation contradicts this, and the upgrade kit did not come with a bootable 2.7a disk. Luckily I have one.

Well I have both a bootable 2.7 and 2.7a and they give me problems. The 2.7a disk gives me the error listed above. The 2.7 disk actually works and lets me go through the steps and asks for the next dvd disk, but when it puts the OS on it reboots to a blue screen. I have opened a case and will see what TAC tells me about this.

We think we have an answer. We noticed our server is not listed in the approved hardware list and for 2000.2(6), but is in the Approved hardware list for CallManager???

The difference, the model server we have came with a CD-ROM drive. The media (disk 2 and above) are on DVD-ROMs. Du-ohh! this only took 3 days for us to figure out. No response from Cisco. But we are pretty sure this is the imcompatibility.

We were assured the following solution would be okay: find a copy of 2000.2(4) which should be on CD-ROMs only and them upgrade, upgrade, upgrade.