Tuesday, February 19, 2013

Message Waiting Indicator (MWI) issue between Avaya Aura Communication Manager and Exchange Server 2010 Unified Messaging Integration


You currently have the following telephony solution in your organization:

PBX: Avaya Aura Communication Manager Version R016x.02.0.823.0
Voicemail: Exchange Server 2010 Unified Messaging

The Avaya Aura Communication Manager PBX is fully integrated with Exchange Server 2010 Unified Messaging with MWI (Message Waiting Indicator) functioning as expected but you recently noticed that the MWI is either permanently off or lit up regardless of whether users have voicemails:



While there can be many reasons that can cause this problem, I recently found that this can happen if the Exchange 2010 Mailbox Server’s Microsoft Exchange Mailbox Assistants (MSExchangeMailboxAssistants.exe) service is stopped:


Basically what happens when this service is stopped is the following:

MWI not already lit up on the phone – New voicemails received will not light up the MWI light

MWI already lit up on the phone – MWI light will continue to be lit even after all voicemails have been listed to or deleted

This can be fixed by simply restarting the service.

1 comment:

Anonymous said...

Hi Terence,

I am curently trying to integrate Exchange 2010 SP3 with AVaya CM via SM 6.3.7. I have call flow working, however, my MWI doesn't work at all. Is it possible for you to let me know the config on CM, SM and Exchange? Specially the PORT used in between. I am having port 5060 TCP used between CM & SM. From SM to Exchange I have port 5060 ( SM side) and 5067 (UMSide). I can see the MWI delivered from Exchange UM to Avaya SM and from Avaya SM to Avaya CM. On Avaya CM it fails complaining that "400 Bad Request message-account - 1".... Any idea. you can post me the response on patel77 at gmail dot com.

Thank you in advance.