IPO Server Edition 9.1.3
Exchange 2010 updated
MAPI plugin 9.1.3 w/Outlook 2010 on Server 2008 R2
I'm having trouble with some UMS users where their old message count includes voicemails that have already been deleted. If you check the old messages on the phone, it gives the header information, but doesn't play the WAV, because it was deleted from the users email account already. If the user deletes it from the phone, it doesn't clear it out. All new messages seem to be received and deleted properly. The .lastats.txt file increments up and down properly. I think this might be because Exchange UM is sending unsolicited message updates, and my failure is specific to solicited updates.
If I disable the MAPI service on the MAPI relay server, then restart the voicemail service, all the UMS users .lastats.txt files zero out like expected (0,0,0,0). Then when I bring the MAPI service back up, the voicemail server syncs up and populates the users .lastats.txt file again, but it still has the phantom old messages (0,0,12,0). This leads me to believe the Exchange environment is not properly recording UM message statuses properly. I haven't the foggiest idea how to check this though. It doesn't appear that there is any way to view an Exchange users voicemail stats. Get-UMMailbox | fl doesn't provide any relevant data. Does anyone have any tips on how to view this info? I know this is not an Exchange forum.
Here is something suspect I see in the debug log. I get the below message periodically for every UMS user. Does anyone know what this implies? CMAPIImpl::GetCounts failed makes me think the MAPI relay can't pull message counts properly, but then right after each of these errors, I see a successful message.
14/08 09:01:42.911 vmpro (19,1) 5b38,02821b70,23998: CMAPIImpl::GetCounts failed
14/08 09:01:43.021 vmpro (19,5) 5b38,02821b70,23998: Successfully requested email notifications for mailbox "username".
I have reinstalled / reconfigured the MAPI plugin.
Reset user voicemail profile from VMPro CLient.
Created a new mail profile for the MAPI relay.
Disabled the users voicemail and re-enabled.
Switched the users voicemail to VMPro and then back to UMS and Forward.
Exchange 2010 updated
MAPI plugin 9.1.3 w/Outlook 2010 on Server 2008 R2
I'm having trouble with some UMS users where their old message count includes voicemails that have already been deleted. If you check the old messages on the phone, it gives the header information, but doesn't play the WAV, because it was deleted from the users email account already. If the user deletes it from the phone, it doesn't clear it out. All new messages seem to be received and deleted properly. The .lastats.txt file increments up and down properly. I think this might be because Exchange UM is sending unsolicited message updates, and my failure is specific to solicited updates.
If I disable the MAPI service on the MAPI relay server, then restart the voicemail service, all the UMS users .lastats.txt files zero out like expected (0,0,0,0). Then when I bring the MAPI service back up, the voicemail server syncs up and populates the users .lastats.txt file again, but it still has the phantom old messages (0,0,12,0). This leads me to believe the Exchange environment is not properly recording UM message statuses properly. I haven't the foggiest idea how to check this though. It doesn't appear that there is any way to view an Exchange users voicemail stats. Get-UMMailbox | fl doesn't provide any relevant data. Does anyone have any tips on how to view this info? I know this is not an Exchange forum.
Here is something suspect I see in the debug log. I get the below message periodically for every UMS user. Does anyone know what this implies? CMAPIImpl::GetCounts failed makes me think the MAPI relay can't pull message counts properly, but then right after each of these errors, I see a successful message.
14/08 09:01:42.911 vmpro (19,1) 5b38,02821b70,23998: CMAPIImpl::GetCounts failed
14/08 09:01:43.021 vmpro (19,5) 5b38,02821b70,23998: Successfully requested email notifications for mailbox "username".
I have reinstalled / reconfigured the MAPI plugin.
Reset user voicemail profile from VMPro CLient.
Created a new mail profile for the MAPI relay.
Disabled the users voicemail and re-enabled.
Switched the users voicemail to VMPro and then back to UMS and Forward.