Doubts-Regarding Cisco unity integration

[Trying tobeone]

One of our client is planing to add cisco unity to the setup. Currently we dont have an AD or exchange for them in our premise as its an offshore development center.
Our CUCM is 7.1 and Unity is 7, which is going to be installed on VMWare

As am newly appointed and am not aware about Unity.. can anyone throw some light on this regarding,

1, Steps for Unity installation on VMWare
2, How to go ahead like what all requirements i have to put in front of the client, like AD and Exchange.

I read that voice messages are stored in Exchange, so in that case, is AD mandatory?
Also am not able to get a full idea on working of Unity.. if some one can share some documents, it would be really grateful..

Regards
TT

[William Bell]

TT,

I hope that you have adequate time and equipment to practice on before building this live. Unity is one of the more complicated applications when you get started with it. Fortunately, the documentation on getting Unity on line is plentiful. You must ensure you read the installation guide thoroughly.

Here are the Cisco Unity install guides:

http://www.cisco.com/en/US/partner/products/sw/voicesw/ps2237/prod_installation_guides_list.html

Start in the 7.x section but please note that the 5.x install guides are used for 7x installs as well.

Design guide for Unity virtualization:

http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdgx.html

I don't know if you have options, but I would recommend that if you are looking to do a new build that you look at Unity Connection instead of Unity. Unity Connection is getting the bulk of Cisco's development investment. Unity is being maintained but don't expect it to get new features.

HTH.

Regards,

Bill

[David Hailey]

Definitely agree with Bill on this one.  If this is a new deployment, you should look to garner traction for Unity Connection and not traditional Unity.  Depending on the feature set that the client requires, you'll find that the requirements for Unity Connection are a bit easier to comply with because it is very flexible in terms of deployment options particularly on a per-user basis.

If you do go with Unity, it will require that you have Active Directory and Exchange in place.  In a "voicemail" only deployment, the AD/Exchange would only be used to enable Unity functionality.  In a Unified Messaging deployment, this would be an existing customer environment and, in most cases, you are going to need to field A LOT of questions.

Hailey

[Rob Huffman]

Hi TT,

Sorry to jump in but i just wanted to add these links to the awesome

info from Bill and Hailey (+5 each!)

Maybe you can show these notices to management to help your cause along;

• End-of-Sale and End-of-Life Announcement for the Cisco Unity 8.0
  01/Aug/2011
• End-of-Sale and End-of-Life Announcement for the Cisco Unity 7.0
  01/Aug/2011

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_eol_notices_list.html

Cheers!

Rob

[Trying tobeone]

Thanks Bill, Hailey and Rob...

As always you people came on time for help...

In addition, the customer is looking for Unity only.

I have gone through the install and design guides, but as i said am new to unity, may i get some docs which will help in basic level understanding of how the messages will saved and how it will be integrated to the user's mailbox.

Regards

TT