MWI not sync'ing with Unity and Exchange Server in different VLAN's

[staubach-cco]

We have a Unity server running 4.0.3 SR1, with unified messaging for users on 3 Exchange Servers that are located in a different "Server" vlan. Users who have their mailboxes on the "Partner" Exchange Server that Unity talks to are having issues with the MWI either staying on when their messages have been read, or not coming on when they have a new message. This does not happen to either of the 2 other Exchange Servers. When we move the Unity server into the same vlan as all the Exchange servers, the problem goes away. We are running Exchange 2000 SP3 on top of Windows 2000 SP4. I've checked the network card settings and statistics, no errors or dropped packets at all. Same for all the switch ports. All servers are connected to a Cisco 6509. I've gone through the process of manually resyncing each mailbox as the problem arises, having them dial the code to turn MWI light on/off from their phone and resync'd MWI on the entire system. Since the problem doesn't seem to exist with either of the other 2 servers at all, I'm assuming the problem does not lie with Unity, but with that particular Exchange server. It is a Compaq DL380 G2 with plenty of RAM and CPU.

[Hin Lee]

1) Do you have outlook installed on the exchange server? Unity?

2) Is Exchange 2000 Sp3 installed on Unity?

3) Open Unity Diagnostic Tools (UDT), set Macro Traces for MWI - TAPI. On UDT, click on Start New logs

4) Open Port Status Monitor (PSM) and monitor the last 4 ports.

5) Click on "Refresh Status" on one subscriber homed to the Partner server

6) Does PSM show MWI dial out for the subscriber's extension?

7) "Gather logs" from UDT - Choose "Select Logs". Expand AvCsMgr, and select the last file. Repeat for AvMsgStoreMonitorSvr. Post the logs and tell me the name of the subscriber.

H. M.

[j.house]

I am currently having the same issue. Were you ever able to find out a resolution to this issue?