Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

MWI problem on 4.2

Hi I have recently upgraded from Call Manager 4.1 to 4.2. The users are now reporting that their MWI is not alerting them when they get a message, but it is being delivered to the Exchange inbox. I have noticed that when I dial the MWI on extension number I now get a busy tone, where as before it instantly ended the call. When I resync the unity server I notice it takes around 30 seconds for the MWI call to complete when monitoring the unit port status. Does anyone know if this is a known issue with 4.2 and of any fixes.

Thanks in advance.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: MWI problem on 4.2

Check to make sure you have upgraded the TSP software on Unity. This is usually the problem with TSP.

If you have a large number of Unity subscribers, syncing mailboxes take a couple minutes. If you have only 50 boxes, it should go less than 30 seconds.

You may also want to check your Unity server settings for port settings. Typically, you should reserve 25 percent of your ports for MWI use only. These ports do not answer calls for vm. This will ensure you do not get busy signals as MWIs get turned on or off.

You can change this setting in the UTIM in Unity Tools at the console.

Also, if the subscriber has a rule setup in Exchange to move a message from the Inbox to a subfolder if it's a voicemail, Unity will turn the light on, but as soon it is read or moved out of the Inbox, it will turn the light off. Rules in Outlook usually screw with this.

hope this helps.

3 REPLIES

Re: MWI problem on 4.2

Check to make sure you have upgraded the TSP software on Unity. This is usually the problem with TSP.

If you have a large number of Unity subscribers, syncing mailboxes take a couple minutes. If you have only 50 boxes, it should go less than 30 seconds.

You may also want to check your Unity server settings for port settings. Typically, you should reserve 25 percent of your ports for MWI use only. These ports do not answer calls for vm. This will ensure you do not get busy signals as MWIs get turned on or off.

You can change this setting in the UTIM in Unity Tools at the console.

Also, if the subscriber has a rule setup in Exchange to move a message from the Inbox to a subfolder if it's a voicemail, Unity will turn the light on, but as soon it is read or moved out of the Inbox, it will turn the light off. Rules in Outlook usually screw with this.

hope this helps.

New Member

Re: MWI problem on 4.2

Hi,

Thanks for the reply, I'll pass this on to our unity enginner and let you know how it goes.

Kind regards

Richard

New Member

Re: MWI problem on 4.2

Worked first time Many thanks

129
Views
0
Helpful
3
Replies