Yep, we messed up. Upgraded to Exchange 2003 (separate box) without first upgrading Unity. We're on Unity 3.1(5) and had disks for 4.0(2) but hadn't installed it.
Turns out we need 4.0(3) or better, but my question is, assuming we get the right software, is there any way of recovering our situation going forward? We'd like to return to fully integrated messaging as soon as possible, but an incremental approach can work if it's possible.
Assuming we get the latest version of Unity for the SPE, can we upgrade our current install 3.1(5) while it's down like this? All I get is a system log error about AvCsMgr service terminating unexpectedly when I try to restart Unity.
Is there any way to alter the current install so it doesn't integrate with Exchange, but does handle incoming call answering and use it's own message store?
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...