Unity has now been rebuit from 4.0.3 to 4.2 onto new hardware from a DIRT backup.
Same problem still exists. MWI works for a while and then stops - ie if its on it stays on after deleting messages and if the subscriber receieves a new msg it doesnt illuminate. All ports are enabled for dialout and MWI.
It tends to start working about 1 hr after Unity is rebooted then stops working about 1hr afterwards.
The partner server is local to Unity (Exchange 2000 sp3) There are 12 other message store Exchange servers distributed across sites. I know this is not recommended for UM but not sure what symptoms to expect from this design.
I am not certain if this has ever been stable as have taken over from a previous maintenaince provider.
Once it has failed and I leave a message port status monitor does not show any ports dialling MWIs for mailboxes.
I noticed that the Exchange boxes hadnt been rebooted for about 1 year so rebooted those but its still the same.
I'm now trying to understand whether this is a Cisco or MS Exchange problem. I would have thought it is Exchange but then why would the ports not be dialling out for MWI?
I have followed the troublshooting MWI document and I am still none the wiser. It just says to gather micro traces but not what to do with the traces!
Unity is able to ping all of the Exchange servers.
Does anybody have any ideas? Should I be thinking about a new clean installation or is it a network problem?
There is nothing that really stands out in the event logs - I can post them if needs be.
Thanks for your time reading this.