on 09-15-2009 09:20 AM
[toc:faq]
The UC 500 Software Packs bundle all the necessary files for the UC 500 Series platform. The files include UC 500 IOS image, voicemail and automated attendant CUE software, IP Phone firmware files, and multiple TAR/archive files for various components of the UC 500 (for example vlan information, default configuration files for each product SKU, ringer files for IP Phones, music-on-hold files, background images for colored IP Phones, etc.). The UC 500 Software Packs are thoroughly tested with CCA releases and are pre-installed on UC 500 shipped from Cisco.
For any questions relating to the UC 500 Software Packs please email uc500-swp@cisco.com.
To download the latest UC 500 Series software go here:
https://supportforums.cisco.com/docs/DOC-9829/
For the latest CCA software go here:
http://www.cisco.com/go/configassist
For the latest OM software go here:
http://www.cisco.com/go/officemanager
Note: Timelines & Releases are tentative and are subjected to change
Software Pack | Release Timeframe | IOS | CME | CUE | Compatible CCA |
---|---|---|---|---|---|
8.6.2 | 2013-JUL | 15.1(4)M6 | 8.6 | 8.6.5 | 3.2.3 |
8.6.1 | 2012-NOV | 15.1(4)M5 | 8.6 | 8.6.5 | 3.2.2 |
8.6.0 | 2012-JUN | 15.1(4)M4 | 8.6 | 8.6.3 | 3.2.1 |
8.2.0 | 2011-JUL | 15.1(2)T4 | 8.1 | 8.0.6 | 3.1 |
8.1.0 | 2010-DEC | 15.1(2)T2 | 8.1 | 8.0.3 | 3.0 |
8.0.5 | 2010-NOV | 15.0(1)XA3a | 8.0 | 8.0.3 | 2.2.6 |
8.0.4 | 2010-AUG | 15.0(1)XA3a | 8.0 | 8.0.2 | 2.2.5 |
8.0.3 | BETA1 | 15.0(1)XA3a | 8.0 | 8.0.2 | 2.2.5 (Beta) |
8.0.2 | 2010-MAR | 15.0(1)XA2 | 8.0 | 7.1.3 | 2.2.2 |
8.0.1 | 2010-FEB | 15.0(1)XA1a | 8.0 | 7.1.3 | 2.2.2 |
8.0.0 | 2009-NOV | 15.0(1)XA | 8.0 | 7.1.3 | 2.2 |
7.0.4 | 2009-OCT | 12.4(20)T4 | 7.0 | 7.0.3 | 2.1.1 |
7.1.3 | 2009-SEP | 12.4(24)SB | 7.1 | 7.0.3 | 2.1 |
1. Software Pack 8.0.3 was only released as a BETA release.
2. Software Pack 8.0.5 was an unplanned release in response to CSCti85760
Software Pack | SPA-525G | SPA-50X SPA-30X |
SPA 51x | 7914 | 7915 7916 | 7921 7925 | 7936 | 7937 | 7940 7960 | 79XX | 6901 6911 | 6921 6941 6961 |
8961 9951 9971 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
8.6.2 | 7.5.2c | 7.5.2c | 7.5.2d | 5.0.4 | 1.0.4 | 1.4.1SR1 | 3.3.21 | 1.4.4 | 8.1.2 | 9.1.1 | 9.1.1 | 9.1.1 | 9.2.2 |
8.6.1 | 7.5.2a | 7.5.2b | 7.5.2b | 5.0.4 | 1.0.4 | 1.4.1SR1 | 3.3.21 | 1.4.4 | 8.1.2 | 9.1.1 | 9.1.1 | 9.1.1 | 9.2.2 |
8.6.0 | 7.4.9c | 7.4.9c | 5.0.4 | 1.0.4 | 1.4.1SR1 | 3.3.21 | 1.4.4 | 8.1.2 | 9.1.1 | 9.1.1 | 9.1.1 | 9.2.2 | |
8.2.0 | 7.4.8a | 7.4.8a | 5.0.4 | 1.0.4 | 1.3.4SR1 | 3.3.20 | 1.3.4 | 8.1.2 | 8.5.4S | 9.0.2 | 8.5.4 | -- | |
8.1.0 | 7.4.6 | 7.4.6 | 5.0.4 | 1.0.4 | 1.3.4SR1 | 3.3.20 | 1.3.4 | 8.1.2 | 8.5.4S | 9.0.2 | 8.5.4 | -- | |
8.0.5 | 7.4.4 | 7.4.4 | 5.0.4 | 1.0.4 | 1.3.4SR1 | 3.3.20 | 1.3.4 | 8.1.2 | 8.5.3S | -- | -- | -- | |
8.0.4 | 7.4.4 | 7.4.4 | 5.0.4 | 1.0.4 | 1.3.4SR1 | 3.3.20 | 1.3.4 | 8.1.2 | 8.5.3S | -- | -- | -- | |
8.0.3 | 7.4.4 | 7.4.4 | 5.0.4 | 1.0.4 | 1.3.3 | 3.3.20 | 1.3.4 | 8.1.2 | 8.5.3S | -- | -- | -- | |
8.0.2 | 7.4.3 | 7.4.3 | 5.0.4 | 1.0.4 | 1.3.3 | 3.3.20 | 1.3.4 | 8.1.2 | 8.5.3S | -- | -- | -- | |
8.0.1 | 7.4.3 | 7.4.3 | 5.0.4 | 1.0.4 | 1.3.3 | 3.3.20 | 1.3.4 | 8.1.2 | 8.5.3S | -- | -- | -- | |
8.0.0 | 7.4.2 | 7.4.2 | 5.0.4 | 1.0.4 | 1.3.3 | 3.3.20 | 1.3.4 | 8.1.2 | 8.5.3S | -- | -- | -- | |
7.0.4 | 7.1.9 | 7.1.3c | 5.0.3 | 1.0.3 | 1.2.1 / 1.3.1 | 3.3.16 | 1.3.2 | 8.0.1 | 8.4.2S | -- | -- | -- | |
7.1.3 | 7.1.9 | 7.1.3c | 5.0.3 | 1.0.3 | 1.2.1 / 1.3.1 | 3.3.16 | 1.3.2 | 8.0.1 | 8.4.2S | -- | -- | -- |
A UC 500 Software Pack contains a bundle of various software components resulting to a large zip file - E.g. 300MB. To validate the integrity of the Software Pack before use with CCA the checksum of the Software Pack can be compared to the MD5 checksum posted here. A program like FSUM can be used to compute the checksum-
http://www.slavasoft.com/fsum/
C:\SWP\8.0.5>fsum UC5*
SlavaSoft Optimizing Checksum Utility - fsum 2.52.00337
Implemented using SlavaSoft QuickHash Library <www.slavasoft.com>
Copyright (C) SlavaSoft Inc. 1999-2007. All rights reserved.
; SlavaSoft Optimizing Checksum Utility - fsum 2.52.00337 <www.slavasoft.com>
;
; Generated on 11/30/10 at 17:26:58
;
0a3f57b0a86e31b79cfe44e9503fb376 *UC520_8.0.5.zip
335b94e433d26f2c792e46072000122f *UC540_8.0.5.zip
f49be072816f67e92d3c45aca89a5215 *UC560_8.0.5.zip
C:\SWP\8.0.5>
Software Pack | UC520 | UC540 | UC560 |
---|---|---|---|
8.1.0 | 6daf84694817c48d137dda9581f13df2 | a8daf57fbc3345c08a7f9a3e54a5aa29 | e0e116d1de929bb9f6bf4815ccbad873 |
8.0.5 | 0a3f57b0a86e31b79cfe44e9503fb376 | 335b94e433d26f2c792e46072000122f | f49be072816f67e92d3c45aca89a5215 |
8.0.4 | 262e48b32d94bc281885c763fd62e570 | bce30391a3278c782230defe3b3820bc | 454296bd0024d6b4bc5f005d9f9b357c |
11-30-2010 - Software Pack 8.0.5 and the corresponding CUE localization files have been posted on the Support Community and CCO. SWP 8.0.2 and 8.0.4 along with the corresponding localization files will be removed from the Support Community on 12-3-2010. If these files are needed after their removal they can still be downloaded from CCO, or email uc500-swp@cisco.com to request the specific files needed.
Hi Alberto,
I'd be happy to be able to use the full feature set in 8.6, however due to the ludicrous decision to drop all CLI support in favour of an incomplete and inflexible GUI tool (CCA), there is little hope of that. I was told this was because of support costs, yet my customers were more than happy to spend more to get TAC CLI support to be able to use the features available, rather than the low quality SBSC CCA GUI only support, but they don't have a choice.
You have a solution that doesn't support:
You talk about quality, look above and start there. As our previous requests and concerns have been ignored, I have no doubt these will be also, hence why we've decided to drop this product suite. Your team has also advised us of the long term vision for UC in Cisco and it doesn't include CME, in favour of Cisco Business Edition. No CME = No UC500.
We have supported this platform since its inception, only to find we are being ignored by the vendor. Partners are angry, and have every right to be.
A smart idea would be to introduce, let's say, a UC600 series, based on ISR G2 technology, fully supported with CLI and CCA, running IOS/CME with appropriate customer selected support levels. Add a couple of EHWIC slots for some WAN connectivity options and you have an unbeatable all in one data/voice/video/wireless SMB platform, but what do I know.
And I agree with the other posts above, the BE3000 is a joke in its current form and feature set.
To say we are bitterly dissapointed at Cisco's handling of the evolution of this product would be a gross understatement. The UC500 platform used to be an asset to our business, now it's a liability.
BE3000 is actually based on the full Cisco Unified Communications Manager (CallManager) product. However, some of the features available on BE5000, BE6000, and the full CallManager product have been disabled in BE3000 8.6. Cisco has plans to enhance the BE3000 platform, including the addition of new features found in the full CallManager product, in future software releases.
John Platts wrote:
BE3000 is actually based on the full Cisco Unified Communications Manager (CallManager) product. However, some of the features available on BE5000, BE6000, and the full CallManager product have been disabled in BE3000 8.6. Cisco has plans to enhance the BE3000 platform, including the addition of new features found in the full CallManager product, in future software releases.
But sales are made with the current product, not promises for the future. Beside, there some important features that not even the full CM of today has, or that require costly and complicated additional products, I name some here: paging, overlay DN to a button, call forward all for non-primary buttons. There are more, and these are what make my customers love the products (some have happily migrated from CM to CME).
I agree with Scott, BE3000 of today is a dud, if Cisco's is betting on it, will get a sound beating, and we partners too.
Paolo,
The issue that I have, is that I am going to be selling this product well into next year, with an eos date of end of the year (although not official). It will make us look bad in a few years when we tell the customer we need to sell them something else that can be supported.
I would look at this way, Cisco has always supported its products atleast 3 years after it has killed it and it annouces EOS atleast 6 months before it kills a product and this is a policy.
The issue that I have, is that I am going to be selling this product well into next year, with an eos date of end of the year (although not official). It will make us look bad in a few years when we tell the customer we need to sell them something else that can be supported.
Absolutely, and here's another point that Cisco is taking the wrong way: trying to shortening the lifespan of phone systems. That It is normally longer than the one of routers and switches (that is already very long in comparison to PCs).
Competitors are still supporting (for hetfy fees) 20 or 30 years old systems. 3 years post-EoS support is ridiculously short, and even 5 is basically showing contempt to customers..
Navin,
I also couldn't agree more with you on this. I want to be able to sell an iphone. My understanding of the BE3000, is that I will be going back to selling a razor.
Sorry, update, I also know that we are unable to sell this product in Canada.
Are there any more releases planned for this product line? I see no updates and nothing planned.
"Are there any more releases planned for this product line? I see no updates and nothing planned." ...
Same question here.
Hi Gregory;
Sorry for the late reply. We are working on a quality release that will be out in the coming weeks. Please stay tuned.
Regards;
Alberto
Alberto Montilla wrote:
Hi Gregory;
Sorry for the late reply. We are working on a quality release that will be out in the coming weeks. Please stay tuned.
That is a great proposition, however I've been informed that the upcoming release will not contain a fix for CSCub52837, that causes packet loss for each new connection to CUE. Honestly I would have hoped something better for a problem initally reported in Aug. '12.
Thanks Alberto, but I was wondering about CME upgrade or other new/enhanced features like full Jabber support ... not a bug fix release.
Thanks.
Gregory Laub wrote:
Thanks Alberto, but I was wondering about CME upgrade or other new/enhanced features like full Jabber support ... not a bug fix release.
As discussed before, al indications are that Cisco has decided to cut development short, and leave UC500 at the current IOS level of 15.1M (that was actually released two years ago for the equivalent ISR G1 or G2 platform). We are now just awaiting for the upcoming end of sales announcement.
Of course my apologies if I'm wrong, in case Cisco would change their mind, and announce anything different from the above.
I am also 100% annoyed at Cisco's attitude to this product, it seems the only option will be to sell CME via ISRg2s which is a *lot* more expensive. BE3000 seems like a new platform completely that doesn't follow any existing Cisco product line and for this reason alone I will not touch it, even if it did work. For larger customers a discounted BE6000 seems the only option, but honestly I'm looking at LYNC 2013 or Hosted LYNC for my SME customers.
Cisco are going to lose the SME market completely if they do not announce a UC600(ISRg2) very shortly, as I for one refuse to sell BE3000 or that even more awful UC300 and I am sure I'm not alone.
Very disappointed with Cisco, even our Express Unified Communications Speciality does not have a direct replacement, aparently I have to hire a few more CCNPs (which I do not need and can't afford).
Anyone know if support for the 8961, 9951/71 side card (CP-CKEM) is it on the roadmap for the UC500?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: