Unity 4.0.4 on Windows 2003 and using Exchange 2003.
Unity is configured for failover, so have two Unity servers.
CallManager 4.0.1 es30
Unity Pilot is 1900.
Unity ports are from 1901 to 1972
Problem:-
After processing random number of calls, Unity will lock the first two voicemail ports, 1901 and 1902. So, if you call Unity pilot now, you get RNA. If you call the ports individually, then calling 1901 and 1902 gives RNA; but 1903 onwards is answered by Unity just fine. Resetting the voicemail ports from CCMAdmin doesn't help. A restart of Unity will help resolve the problem.
If Unity is not restarted, and the first two ports are locked, then you place calls to Unity pilot and keep getting RNA. Eventually the Unity service, AvCsMgr, on primary Unity server will go down, and a red X appears on the Unity tray icon. At this point secondary Unity server should answer calls, but it doesn't pick up the call, and gives RNA simply. When you call Unity, you can see that the call is going to Unity secondary server, by looking at the name display for the voicemail port, but you just get RNA.
When primary Unity server comes back online (manual restart), then Unity again starts answering calls correctly, until a random time when the problem starts again.
This has been happening since install.
