Jabber MWI Issue

[Amit Kumar Sharma]

We have configured the User mail box with Alternate numbers. MWI is working for the hard phone but with jabber it is not showing. Is there any particular configuration for Voice mail with Alternate numbers in case of jabber.

CUCM version: 14.0

Jabber version: 14.0

CUC version: 14.0

Quick help will be appriciated.

[M02@rt37]

Hello @Amit Kumar Sharma,

When a user has alternate numbers configured for their mailbox, Cisco Unity Connection should send MWI notifications to all of the registered devices associated with the user's primary extension, including their hard phone and Jabber. However, there are a few things you can check to ensure that MWI is working properly for Jabber users:

--Verify that Jabber users are associated with their primary extension in CUCM. In the CUCM Admin interface, go to the user's Device Association page and make sure that their Jabber device is associated with their primary extension.

--Check the MWI configuration for Jabber. In the CUCM Admin interface, go to the Jabber Service Profile Configuration page and make sure that the "Enable Message Waiting Indication" option is checked.

--Verify that the Jabber client is configured to receive MWI notifications. In the Jabber client, go to File > Options > Voicemail and make sure that the "Show message waiting indicator" option is checked.

--Check the MWI settings in Cisco Unity Connection. In the Unity Connection Admin interface, go to the user's Alternate Numbers page and make sure that the "Message Notification" option is set to "On" for each alternate number.

--Check the MWI synchronization settings in Unity Connection. In the Unity Connection Admin interface, go to the Message Waiting Indicators page and make sure that the "Synchronize MWIs with UC Service" option is checked.

[Jonathan Schulenberg]

TBH I’m not sure Jabber even consumes the CUCM SIP NOTIFY messages for MWI since it connects to CUC directly. I have always assumed it just read the mailbox new message count directly over that HTTPS connection.

The wording of the OP’s message also makes me wonder if we’re misunderstanding the problem statement. Alternate Extensions on a CUC mailbox have no direct correlation to MWI. Additional MWI Destinations for that mailbox would - but that’s not what they said. If my assumption above is correct, then adding a Jabber user’s DN as an additional MWI destination would have no effect.