Nick--<div><br></div><div>I don't think I understand the "Cisco voice mail earns its keep"? What other factors am I missing?</div><div><br></div><div>Scott<br><br><div class="gmail_quote">On Mon, Apr 5, 2010 at 5:16 PM, Nick Matthews <span dir="ltr"><<a href="mailto:matthnick@gmail.com">matthnick@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><marketing><br>
<br>
FWIW in regards to the 'free' licensing from Microsoft - the general<br>
response is that the licensing is a smaller percentage of the TCO than<br>
you might expect, and the pricing isn't that much different. After<br>
other factors are added is where the Cisco voicemail earns its keep.<br>
<br>
</marketing><br>
<div><div></div><div class="h5"><br>
On Mon, Apr 5, 2010 at 2:15 PM, Scott Voll <<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>> wrote:<br>
> Agreement with Ed.<br>
> In education (maybe more verticals) people are (we included) moving from<br>
> Unity to Exchange 2010 for UM. Exchange 2010 is really cool with the speech<br>
> to text feature. and I get most of it covered under my Microsoft Site<br>
> licensing vs huge maintenance cost from Cisco. I've been screaming at Cisco<br>
> since one of my schools moved to UM exchange 2007 about 3 years ago about<br>
> costs...... Cisco has not moved so we are in the process of moving.<br>
> as for CUPS vs OCS we have been using OCS (again largely covered under M$<br>
> site licensing) for IM / presence and loving it. we will be looking at<br>
> adding the cisco Cookie - moc (or however they spell it) to integrate cisco<br>
> CM with OCS. From my understanding...... most people like OCS better then<br>
> CUPS for features. YMMV.<br>
> as for Call control I still like CM for the price (haven't had the talk with<br>
> my AM about UCL) and Contract center express has helped us with all the<br>
> reporting. CER is a good product also. If price were no object thou, I<br>
> would go with 911enable. but since price is...... CER works fine.<br>
> just my 2 cents<br>
> Scott<br>
><br>
> On Mon, Apr 5, 2010 at 7:13 AM, Jeffrey Ollie <<a href="mailto:jeff@ocjtech.us">jeff@ocjtech.us</a>> wrote:<br>
>><br>
>> On Mon, Apr 5, 2010 at 8:39 AM, Matt Slaga (US)<br>
>> <<a href="mailto:Matt.Slaga@us.didata.com">Matt.Slaga@us.didata.com</a>> wrote:<br>
>> ><br>
>> > With this said, the next release of OCS (now called ‘MCS’) will be a<br>
>> > much closer peer-level with Cisco on the voice side. For now though, the<br>
>> > best of both worlds can be found in integration of the two.<br>
>><br>
>> I'm curious... we have had CallManager/Unity/Contact Center Express in<br>
>> use for several years (although we don't take advantage of as many<br>
>> features as we could). We also have Exchange (2003, soon to be 2010)<br>
>> for our main mail system (our Unity server is in a separate AD<br>
>> forest/exchange store although that's likely to change). There's been<br>
>> some push by our Exchange people to implement some of the OCS<br>
>> functionality for our users.<br>
>><br>
>> Is there really a benefit to going with OCS vs using what we have with<br>
>> Cisco and maybe adding a CUPS server? The promised XMPP integration<br>
>> in CUPS 8 looks very interesting to me. I also need to implement<br>
>> Cisco Emergency Responder soon too.<br>
>><br>
>> --<br>
>> Jeff Ollie<br>
>><br>
>> _______________________________________________<br>
>> cisco-voip mailing list<br>
>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
</div></div></blockquote></div><br></div>