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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Nortel Integration CiscoUnity_MIU 528

I have a Unity 4.04 SR1 server running VMO with off box exchange. The server is dual integrated with Callmanager as one integration and SMDI via PBXLink boxes connected to a Nortel Option 81 as the other integration.

THis setup has worked with minimal issues over the past 1.5 years, but the Nortel integration has recently started failing intermittently and I am having a difficult time figuring out why. The symptom is that the integration will work fine for 4-5 days, and then suddenly and apparently without warning all calls to Unity that originate from the Nortel integration are redirected to the opening greeting.

Once the system fails, the Application log indicates an MIU error # 528 for every incoming call. While the system is in a failed state, the Call Viewer shows all incoming calls with a trunk ID of -1, a dialed number of 0000 and a no information for calling number or forwarding station. Rebooting the servers clears the issue until the next failure occurs (4-6 days typically).

The start of the issue seems to correspond with the removal of 16 ports from the Nortel integration and the subsequent move of these ports to the Cisco integration.

As a part of the troubleshooting process we have rebooted the PBXLinks during failure and the status was not changed. We loaeded ES35 on the Unity server. We verified that the Option 81 is no longer configured to use the removed analog ports that are connected to the Unity Dialogic cards. We verified that the Nortel digital sets are not configured to reference the analog ports that have been removed.

If anyone has any ideas of what may be causing this issue or has suggestions for troubleshooting, your help would be very much appreciated.

-Robert

4 REPLIES
New Member

Re: Nortel Integration CiscoUnity_MIU 528

Just an update to this issue. Since the first post, we have replaced the PBXLink boxes and added a registry key to increase the MutexSleepTimerMS to 1 second from 500 ms. Also, it has occurred to me that the other item that changed immediately preceding this issue was an upgrade of the Unity TSP to version 8.1(3) from 7.04b. I didn't consider this to be a part of the issue previously since I am only having issues with the Nortel integration, but I thought I would mention it just in case.

TAC is insisting the issue is related to bug id CSCef80398, but I'm not convinced since all the cases I have seen involve CallManager ports and problems following server reboots. My problem involves Nortel ports several days after a reboot. If anyone has had a similar issue on a Nortel integration, I would be interested to hear what the fix to your issue was.

-Robert

New Member

Re: Nortel Integration CiscoUnity_MIU 528

Had the exact same issue with an Avaya/Call Manager Dual integration. We were on the exact same software loads with PBX Links and Dialogic cards. It is due to the Dialogic cards getting a voltage spike from the buss of the server. We upgraded our software and servers and went to the PIMG integration on the Avaya side. We are now on Unity 4.1.1 with the PIMG's and have not had a 528 error since. Just our experiences for what it is worth.

Paul

New Member

Re: Nortel Integration CiscoUnity_MIU 528

Thanks for the information, Paul.

If you don't mind my asking, how did you determine that the problem was due to voltage issues on the server? Did you happen to have a Cisco case that I could refer my TAC engineer to?

Thanks Again,

Robert

New Member

Re: Nortel Integration CiscoUnity_MIU 528

Robert,

We never did open a TAC case on this one. It was only taking the PBX ports out of service, so it ruled out the Call Manager side. We were on older servers, so that was the start of our problem. The problem seemed to be more evident after the server was disturbed (ie: reboots or higher memory usage). We just new that from looking at the logs/traces, one port on the dialogic boards caused the issue and took the rest of the dialogic ports out of service. The new PIMG's are so much more stable, it is a good upgrade. Hope this helps!

Paul

118
Views
3
Helpful
4
Replies