[cisco-voip] Difference between Unity Connection and Unity

Pat Hayes pat-cv at wcyv.com
Thu Aug 7 19:08:56 EDT 2008


Just wanted to drop this link as I didn't see anyone mention it yet. Feature
by feature comparison of Unity, UC, and CUE:

http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps5745/ps2237/product_data_sheet0900aecd806bfc37_ps6509_Products_Data_Sheet.html



On Thu, Aug 7, 2008 at 3:52 PM, Matthew Saskin <matt at saskin.net> wrote:

> What does that get you though?  A unity pair in one location is still a
> single point of failure if it serves users outside of that location.
>
>
> Jonathan Charles wrote:
>
>> Yes, but I can install failover pairs in cities around the world to the
>> same Unity organization... with no theoretical limit on maximum size.
>>
>>
>>
>> Jonathan
>>
>>
>> On Thu, Aug 7, 2008 at 12:19 PM, Matthew Saskin <matt at saskin.net <mailto:
>> matt at saskin.net>> wrote:
>>
>>    All the various tools for CUC 2.x are built into the RTMT.  Yes, you
>>    use the same RTMT to connect to CUC and CallManager.
>>
>>    Also in reference to an earlier post, you can't officially split
>>    Unity FO pairs between multiple data centers.  Last I looked at the
>>    SRND they need 100mbps lan between the boxes.  That said, I've done
>>    it with very mixed results in the past.
>>
>>    -matt
>>
>>    Weigand, John V. wrote:
>>
>>
>>        Litigation Management
>>
>>
>>        Serious Medicine for the Defense (R)
>>        <http://www.medicineforthedefense.com/>
>>
>>
>>
>>        At least on UC 1.2x, it has a call viewer, port status monitor,
>>        and can backup directly to anywhere without SFTP. Has all that
>>        changed with the 2.x appliance version?
>>
>>
>>               *John V. Weigand*
>>        Help Desk Support/Executive Support
>>
>>        Litigation Management, Inc.
>>        300 Allen-Bradley Drive
>>        Suite 200
>>        Mayfield Heights, OH 44124
>>
>>
>>
>>
>>
>>        Tel: 440-484-2000
>>        Fax: 440-484-2009
>>        Cell:
>>        email: <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>> jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>
>>        <mailto:jvw at medicineforthedefense.com
>>        <mailto:jvw at medicineforthedefense.com>>
>>
>>
>>
>>        PRIVILEGE AND CONFIDENTIALITY NOTICE
>>
>>        The information in this electronic mail is intended for the
>>        named recipients only. It may contain privileged and
>>        confidential material and may be protected under law by the
>>        Health Insurance Portability and Accountability Act. Any use of
>>        this information by anyone other than the intended receiver is
>>        prohibited. If the reader of this message is not the intended
>>        recipient, you are hereby notified that any dissemination,
>>        distribution, copying, or other use of this message or its
>>        attachments is strictly prohibited. If you have received this
>>        message in error, please notify the sender immediately by
>>        replying to this electronic e-mail or by calling (800) 778-5424.
>>        Please delete it from your computer. Thank you.
>>
>>        *From:* cisco-voip-bounces at puck.nether.net
>>        <mailto:cisco-voip-bounces at puck.nether.net>
>>        [mailto:cisco-voip-bounces at puck.nether.net
>>        <mailto:cisco-voip-bounces at puck.nether.net>] *On Behalf Of
>>        *Jonathan Charles
>>        *Sent:* Thursday, August 07, 2008 9:51 AM
>>        *To:* Tim Smith
>>        *Cc:* JASON BURWELL; Cisco VoIP
>>        *Subject:* Re: [cisco-voip] Difference between Unity Connection
>>        and Unity
>>
>>                To be honest, all this being said, I would  much rather
>>        deploy/manage Unity than UC...
>>
>>        First off, no real tools in UC to diagnose a problem (no call
>>        viewer, no port status monitor...) and it has that silly
>>        SFTP-only backup solution.
>>
>>        Also, it seems childish... this may be mystique, but when I see
>>        CUC on a site, I assume they were too cheap to buy Unity...
>>
>>        However, for VM-only it is a decent idea... doesn't make much
>>        sense to buy full-blown Unity, with Windows 2003, Exchange and
>>        SQL licensing, just to give voicemail to 100 users.
>>
>>        To be honest, I really don't deal with small customers that
>>        would think CUC would be a solution... the one time I did do a
>>        CUC install, the customer bought IMAP licenses (so it was the
>>        same price as Unity) and they complained constantly about how
>>        awful IMAP was...
>>
>>
>>
>>
>>        Jonathan
>>
>>        On Thu, Aug 7, 2008 at 12:31 AM, Tim Smith <thsglobal at gmail.com
>>        <mailto:thsglobal at gmail.com> <mailto:thsglobal at gmail.com
>>
>>        <mailto:thsglobal at gmail.com>>> wrote:
>>
>>        No resilience in Unity Connection (currently) - heard rumours it
>>        should be there in version 7.
>>
>>        No networking in Unity Connection (again currently) - so it is
>>        stand alone.
>>
>>                Unity can support Domino as a message store in both VM or
>> UM -
>>        done this a couple of times, and I hate it.. just quietly :)
>>
>>                Unity is more scalable.. as already mentioned.
>>
>>                UC is voicemail in a box.. quick and easy to setup and
>> manage..
>>        no Microsoft skills required anymore..
>>
>>        Simple voice mail, and you are under the right number of users
>>        (and you can live with no resilience for now) - then UC is a
>>        good choice. The appliance model is great. It also has some of
>>        the advanced features that some of your users may require. I
>>        think someone already mentioned there is some cool integration
>>        with Exchange calendars and personal call routing rules.
>>
>>                Unity is an "adventure" to setup and manage :) and will
>> usually
>>        require Microsoft integration skills as well..
>>
>>        Unity has lots of flexibility for deployment options to consider
>>        also..
>>
>>                If you have a large complex deployment, sure you could end
>> up
>>        with multiple UC servers. But more likely you would look at full
>>        Unity, and run failover pairs split across 2 x data centers..
>>
>>                And of course if you want voicemail, email and faxes to all
>>        co-exist in 1 big mailbox for each user.. then you have no
>>        choice.. Unity all the way.
>>
>>                If you do talk Unity to a customer, you need to discuss
>>        thoroughly the possible impact and integration with their
>>        existing network..
>>
>>                Cheers,
>>
>>                Tim
>>
>>                On 8/6/08, *JASON BURWELL* <JASON.BURWELL at foundersfcu.com
>>        <mailto:JASON.BURWELL at foundersfcu.com>
>>        <mailto:JASON.BURWELL at foundersfcu.com
>>        <mailto:JASON.BURWELL at foundersfcu.com>>> wrote:
>>
>>           *Table 4.* Cisco Voice and Unified Messaging Products
>>
>>           *Product*
>>
>>
>>           *Number of Users*
>>
>>
>>           *E-Mail Integration Options*
>>
>>
>>           *Networking to Other Voicemail Systems*
>>
>>
>>           *Integration with Third-Party Call Processing*
>>
>>
>>           *Speech Recognition*
>>
>>           Cisco Unity Express
>>
>>
>>           Up to 250
>>
>>
>>           Integrated
>>
>>
>>           Yes, with Cisco Voice and Unified Messaging products
>>
>>
>>           No
>>
>>
>>           No
>>
>>           Cisco Unity Connection
>>
>>
>>           Up to 7500
>>
>>
>>           Integrated
>>
>>
>>           Yes, with Cisco Voice and Unified Messaging products
>>
>>
>>           Yes, with most traditional and IP private branch exchanges
>> (PBXs)
>>
>>
>>           Yes
>>
>>           Cisco Unity Unified Messaging
>>
>>
>>           7500 per server, networked to 250,000
>>
>>
>>           Integrated and Unified Messaging (Microsoft Exchange, Lotus
>>        Notes,
>>           or Novell GroupWise)
>>
>>
>>           Yes, with Voice Profile for Internet Mail (VPIM), Audio
>> Messaging
>>           Interchange Specification (AMIS), Cisco Unity Bridge, etc.
>>
>>
>>           Yes, with most traditional and IP PBXs
>>
>>
>>           Yes
>>
>>                                         Found at this link
>>
>> http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/vcallcon/ps556/product_data_sheet0900aecd80410ad6_ps6509_Products_Data_Sheet.html
>>
>>                                         Jason Burwell
>>
>>           Telecom Network Administrator
>>
>>           Founders Federal Credit Union
>>
>>
>> ------------------------------------------------------------------------
>>
>>           *From:* cisco-voip-bounces at puck.nether.net
>>        <mailto:cisco-voip-bounces at puck.nether.net>
>>           <mailto:cisco-voip-bounces at puck.nether.net
>>        <mailto:cisco-voip-bounces at puck.nether.net>>
>>           [mailto:cisco-voip-bounces at puck.nether.net
>>
>>        <mailto:cisco-voip-bounces at puck.nether.net>
>>           <mailto:cisco-voip-bounces at puck.nether.net
>>        <mailto:cisco-voip-bounces at puck.nether.net>>] *On Behalf Of
>>        *Aman Chugh
>>           *Sent:* Wednesday, August 06, 2008 1:20 PM
>>           *To:* cisco voip
>>           *Subject:* [cisco-voip] Difference between Unity Connection
>>        and Unity
>>
>>
>>           I have always tried to understand what is the difference between
>>           Unity Connection and Unity and when to sell Unity and Unity
>>           Connection . Looking for differences in architecture of these
>>           applications and how they work with Exchange.
>>
>>
>>           TIA
>>           Aman
>>
>>                     _______________________________________________
>>           cisco-voip mailing list
>>           cisco-voip at puck.nether.net
>>        <mailto:cisco-voip at puck.nether.net>
>>        <mailto:cisco-voip at puck.nether.net
>>        <mailto:cisco-voip at puck.nether.net>>
>>
>>           https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>>
>>        _______________________________________________
>>        cisco-voip mailing list
>>        cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>>        <mailto:cisco-voip at puck.nether.net
>>        <mailto:cisco-voip at puck.nether.net>>
>>
>>        https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>>
>>  ------------------------------------------------------------------------
>>
>>        _______________________________________________
>>        cisco-voip mailing list
>>        cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
>>        https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>>
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080807/e432ccff/attachment-0001.html>


More information about the cisco-voip mailing list