[cisco-voip] Unity 5.0(1) UM, MWI not working

[Ian du Preez]

I have installed Unity 5.0(1) in Unified messaging with Exchange 2007
partner and CCM 6.
Exchange 2007 cluster running on Windows 2003.
MWI is not working system wide. I have run through the MWI troubleshooting
guide with no
luck.
All the basic stuff in CCM does work and from the phones I can dial MWI on
and off
numbers.
The VM ports can also dial. The VM ports are registered, so I do not think
it is the CCM
integration.

Users do get voicemail in their outlook inbox. They do not get the MWI on,
on the phone.
When they then access their messages from the phone, Unity tells them that
there are no
messages.
Even though they are in the outlook inbox.

I open the PortStatusMonitor to monitor the last ports. When I refsync all
the MWI’s in
the UTIM this below shows on the port. :
Dialing (MWI – cancel) ‘xxxxxxxxxx’
This is the same when I leave a new message for a user.

I found bug CSCsu80743 referring to this problem.
I installed ES70 and ran through this info in the readme file and did the
registry
setting, and restarted Unity :
-------------------------------------------------------
Customers should only enable this functionality when Cisco Unity has
subscribers homed on
Microsoft Exchange 2007 servers configured in a cluster experiencing an
issue with MWIs
identified in the defect. To resolve this issue create the registry key
UseProfileServerNameForMDB here:

[HKLM\Software\Active Voice\ExchangeMonitor]

Registry Key Name: UseProfileServerNameForMDB
Registry Key Type: DWORD
Registry Key Default Value: 0 (Disable new functionality.)

Other Settings:

1 UseProfileServerNameForMDB (Enable new functionality)

Defect: CSCsu80743
-----------------------------------------------------

I still have the exact same problem. I get the Dialing (MWI – cancel)
‘xxxxxxxxxx’
response in the PortStatusMonitor.

I have run through these steps from the troubleshooting file to gather
traces:


10 On the Cisco Unity Diagnostic Viewer screen, click the Configure Micro
Traces icon.
Step 11 Set the following diagnostic traces:
•MiuGeneral—0–4, 12, 16
•MiuIO—11, 14
•MiuMethods—10, 12, 14, 18
•(Circuit-switched phone systems) MiuMethods—20, 22
•MiuIntegration—12
Step 12 On the Cisco Unity Diagnostic Viewer screen, click Start New Log
Files.
Step 13 Leave a message for a subscriber.
Step 14 Review the diagnostic logs to determine the cause of the problems.

-------------------------------------

I can attach those logs in a mail if you require them.
I also have the Gather system Information outputs.
The partner Exchange 2007 server has Service Pack 1 loaded.
On the unity server we have Exchange 2003 Admin tools with Service pack 3
The Unity OS in Server 2003 and Service pack 1.
On Unity we also have SQL 2000 with Service pack 4.

I also have some screenshots of the PortStatusMonitor.
The event viewer does not show any errors.
When I resync the MWI’s in UTIM, the event viewer gives me information that
the resync
started and completed.
But other than that, no errors or MWI information in the event log.
It is a 16 port integration with CCM 6.1.2

After doing some more changes I don’t get the Dialing (MWI – cancel)
‘xxxxxxxxxx’ info in
the PortStatusMonitor any more.
Instead it shows nothing and looking at the users MWI status it sais MWI
request pending.

The users still get VM in their Outlook inbox, but when I try accessing VM
from the phone,
it sais there are no new messages. The MWI lights are also not working
still.

Thanks
Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090507/9a2642be/attachment.html>