We're installing Cisco Unity right now and the ONLY version of SQL server that Cisco is saying they will support with this product is SQL 2000 SP4. This was deprecated in April of 2008 and is out of regular support from Microsoft.
Now for a company like Cisco that prides itself on being the end-all for Network security surely they are not depending on a version of SQL server that is no longer supported by the manufacturer (AKA Microsoft).
Has Cisco Unity been replaced by a newer product line or is Cisco behind the power curve with security? Just wondering if maybe we're not looking at the right product anymore.
Thanks Brandon. It's a little dissapointing that a respected name like Cisco would use out of support products but I understand. I was skeptical when they told me that it was SQL 2000 since it's been out of support for over a year.
So they haven't come out with a product replacement or other option they are trying to move people to instead of Cisco Unity? (Sorry I'm still shaking my head that Cisco would let this happen.)
As I mentioned, the new version of Unity will support SQL 2005. Depending on the size of your deployment, Unity Connection is another option for you. UC is based on a Linux kernel and uses an Informix database instead of SQL.
Just to be clear, Cisco (and many other companies) have extended support contracts for continued support (including fixes if need be) from Microsoft on SQL 2000. Microsoft's support statement for the general public doesn't apply here. Since the SQL installation on the Unity server is specific and dedicated to Unity and any problem you have with that server goes through Cisco support (who can and will open cases with Microsoft as needed) there shouldn't be any issues with being "out of support" here.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...