02-11-2013 09:37 AM - edited 03-19-2019 06:15 AM
In the coming months I hope to be upgrading from Exchange 2003 (sp2) to Exchange 2010 (sp3) running on Windows Server 2012. I currently have Unity 8.0(3.1) running on Server 2003. We hope to be upgrading to Exchange 2013 at the end of the year if that is supported.
Before I contact my Cisco partner about this upgrade I would like to know what to expect. Any advice and suggestions would be appreciated.
Thanks!
Nick
02-11-2013 09:49 AM
The legacy Unity product is EoS/EoL and was End of SW Maintenance at the end of January 2013. There is an integration guide for intergrating Unity with Exchange 2010. You will need to review the documentation for that here:
http://www.cisco.com/en/US/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.html
There are a number of posts in the forum on this topic as well.
Moving beyond 2010 and being supported with Unity is another story given the application status (i.e., this product is no longer being devloped). In general, it's time to consider migrating/upgrading the customer environment from Unity to Unity Connection. However, Unity Connection also does not currently support Exchange 2013...the latest support is currently for Exchange 2010 SP2 as 2013 is still pretty young.
Hailey
Please rate helpful posts!
02-11-2013 12:10 PM
Hi Hailey,
I appreciate the information.
It is very frustrating that Cisco is moving backwards regarding Unity. I view it as a downgrade to move from Unity to Unity Connections. I lose functionality. I no longer get a true unified inbox for my users.
I have had too many of these experiences with Cisco. I know that management will not be happy about this.
Thanks again,
Nick
02-11-2013 12:14 PM
Nick,
You can also integrate Unity Connection with Exchange for Unified Messaging (or Single Inbox) as it's called. What are your concerns in terms of functionality? The integration is much more lightweight and flexible IMO. I prefer it when compared to the traditional Unity setup.
Hailey
02-11-2013 12:20 PM
Ok. I was under the impression that Unity Connection required a separate mailbox. Maybe that has changed? We also use our Unity server as our fax server.
02-11-2013 12:38 PM
The integration is completely different than with legacy Unity. High-level: Unity leverages MAPI integration and is completely dependent upon AD and Exchange to function properly. Hence, the schema extensions, Permissions Wizard (and associated permissions), and etc. Unity Connection leverages web-based APIs for integration. Specifically it uses WebDav for Exch 2003 and EWS for Exchange 2007/2010. It is a dual message store synchronization architecture, which means that 1) it can function independently without AD and/or Exchange integration and 2) no schema extensions and 3) less complicated permissions requirements. With Unity Connection, the users have a mailbox on the server and then a copy of that message is synchronized into the user's corporate Exchange mailbox. You get MWI synchronization between phone and email and etc (hence, you get Unified Messaging). Another nice thing is that you can handle requirements for voicemail only scenarios locally on Unity Connection without having to create dummy or "resource" AD/Exchange accounts in the corporate systems. You can read up more on this integration here and hit me back up if you have questions. I'll be glad to help if I can.
As for the fax part, OK - that's a problem in your scenario. Personally, I've never been a big fan of using Unity for that (and don't) but then again, I don't really like "fax" anyway. Personal opinions aside, I'll go with relay of facts. Unity Connection supports integration with 3rd-party fax systems. You can take a look at that here:
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/design/guide/8xcucdg080.pdf
In terms of Unity though, the reality is that it's days are (and have been) numbered. See below:
Hailey
Please rate helpful posts!
02-11-2013 12:42 PM
That's a lot of great information.
Thank you!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide