12-20-06 12:11 AM
So, it is all vaporware...
We were given an official launch breifing less than a year ago, by Cisco,
that gave the release train index.
This is how it was laid out:
CCM5.0 would have feature parity with 4.1 (with SIP crap), and would be
released March 7 (or so) 2006.
CCM5.1 would have feature partity with 4.2 and would be released at end of
CY2006 (which they did).
CCM6.0 would be platform independent and Appliance and Windows versions
would have feature parity and licensing for both, and would be released end
of CY2007.
So, they seem to be hitting their release dates, but blowing off their
feature releases.
Let me guess, the Windows version with SIP support will be released in 2009
on version 8.0 of CCM...
Jonathan
On 12/19/06, Matt Slaga (US) <Matt.Slaga@us.didata.com> wrote:
>
> There is no feature parity with 4.2/5.1 yet. Also, 6.0 lost the "OS
> independent" option as well.
>
> ------------------------------
> *From:* cisco-voip-bounces@puck.nether.net [mailto:
> cisco-voip-bounces@puck.nether.net] *On Behalf Of *Jonathan Charles
> *Sent:* Tuesday, December 19, 2006 3:00 PM
> *To:* Wes Sisk
> *Cc:* cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] ETA for CallManager 5.1 on CCO?
>
> Wait a second here...
>
> I just read the readme for 5.1(1) and I was told (officially) that CCM5.1
would be based on
> CCM4.2 and would have 4.2 features.
>
> There is no mention of Log In To Hunt Group or CFUR...
>
>
> We was robbed!
>
>
>
> Jonathan
>
> On 12/19/06, Wes Sisk <wsisk@cisco.com> wrote:
>
> ------------------------------
>
> * Disclaimer: This e-mail communication and any attachments may contain
> confidential and privileged information and is for use by the designated
> addressee(s) named above only. If you are not the intended addressee, you
> are hereby notified that you have received this communication in error and
> that any use or reproduction of this email or its contents is strictly
> prohibited and may be unlawful. If you have received this communication in
> error, please notify us immediately by replying to this message and deleti
ng
> it from your computer. Thank you. *
>
[ Post a follow-up to this message ]
| 
