Unity Miu Error constantly until disable MWI dialout on port

Erick Bergquist · ‎05-26-2005

Get following constantly in event log constantly when port 32 is enabled for dialout MWI. This started happening out of blue this morning and no changes made to the system.

Unity 4.0(4) flat and CCM 4.0(2a) flat

Unity TSP 7.0(4)b

Event Type: Error

Event Source: CiscoUnity_Miu

Event Category: Error

Event ID: 564

Date: 5/26/2005

Time: 1:45:58 PM

User: N/A

Computer: UNITY

Description:

Cisco Unity's telephony component has encountered a serious error.

EXPLANATION:

A serious failure has occurred on port 32 while placing an outgoing call. Most likely, parties involved in the call will be disconnected. In some cases, further calls on this port will not be handled correctly.

TECHNICAL DETAILS:

Thread 0x00002264 had a failure on port 32 in method CAvMiuLine::MakeCall()

DESCRIPTION: HardFailure in Wait after lineMakeCall.

DETAILS:

HCALL: 0x00000000

CallState: LINECALLSTATE_UNKNOWN

DestAddress: 94079816964

LINE_REPLY ErrorCode: 0x8000001C.

CALLINFO:

[13:39:47:771 - 0x00001820] SetMWI(DestAddress 8417 | Messages 1 | State ON) - E_MIU_COLLISION

[13:39:47:787 - 0x00001414] SetMWI(DestAddress 8417 | Messages 1 | State ON)

[13:39:48:193 - 0x00001BAC] LINE_REPLY(0x000101E3 | 0x8000000F)

[13:39:48:193 - 0x00001414] SetMWI(DestAddress 8417 | Messages 1 | State ON) - E_MIU_COLLISION

[13:39:48:208 - 0x00002018] SetMWI(DestAddress 8417 | Messages 1 | State ON)

[13:39:48:568 - 0x00001BAC] LINE_REPLY(0x000101D2 | 0x8000000F)

( Many lines repeating above sequence )

For more information, click: http://www.CiscoUnitySupport.com/find.php . %9

evonnorm · ‎06-02-2005

Is port 32 part of the voicemail hunt group on Cisco CallManager? We recommend isolating dialout ports from those that handle incoming calls, both by removing those ports from the CCM hunt group and by not giving them answer-calls capability in Cisco Unity. The Cisco Unity integration guide for Cisco CallManager discusses how to isolate ports in this way.

You might also try upgrading to TSP 8.0(1), since this could be related to one of the issues we fixed in that release.

Erick Bergquist · ‎06-02-2005

Hi,

I did remove them from the hunt group on CCM and only have dial out MWI checked and the problem still happens.

I did a detailed trace on call manager side, and this port just gets stuck in busy on unity port status monitor webpage when an attempt for MWI dial out happens. The CCM detailed trace has nothing in it from the time frame for this port. If I disable this port and start a new ccm detailed trace and then refresh MWI I do see the MWI activity in the CCM trace on another port that works. That tells me something is hosed up with this port on unity side.

I also reset the unity port via port status monitor which did not help. Our next step is to reboot the server over the weekend since this was working fine and stopped out of the blue.

Does unity dial out MWI by starting at highest port # first - 32 is the last port.

Kapil Atrish · ‎10-31-2011

Hi there,

I am having the exact same issue. Did you get a fix for it?

Cisco Unity 8.0 Build 8.0(3.3)

TSP Version: 8.4(3.3)

CUCM System version: 7.1.3.31900-1

I've verified, this port is not enabled to "Answer call" in Unity and is out of the Line Group in CUCM, still getting the error only for this port. Stragenly, this is not the last or first port. The port range is from 1 to 144, ports 131 to 144 are configured to Dial-Out MWI but not to Answer calls. Errors are being seen only for Port 141.

Event Type: Error

Event Source: CiscoUnity_Miu

Event Category: Error

Event ID: 564

Date: 10/31/2011

Time: 9:43:13 AM

User: N/A

Computer: DCR1-UNITY1

Description:

Cisco Unity's telephony component has encountered a serious error.

EXPLANATION:

A serious failure has occurred on port 141 while placing an outgoing call. Most likely, parties involved in the call will be disconnected. In some cases, further calls on this port will not be handled correctly.

TECHNICAL DETAILS:

Thread 0x00001520 had a failure on port 141 in method CAvMiuLine::MakeCall()

DESCRIPTION: HardFailure in Wait after lineMakeCall.

DETAILS:

HCALL: 0x00000000

CallState: LINECALLSTATE_UNKNOWN

DestAddress: 65259

LINE_REPLY ErrorCode: 0x8000001C.

CALLINFO:

[16:30:09:002 - 0x000021F8] SetMWI(DestAddress 62790 | State ON)

[16:30:09:002 - 0x00000E64] LINE_REPLY(0x00011E07 | 0x8000000F)

[16:30:09:002 - 0x000021F8] SetMWI(DestAddress 62790 | State ON) - E_MIU_COLLISION

[16:30:09:002 - 0x00000620] SetMWI(DestAddress 62790 | State ON)

[16:30:09:018 - 0x00000E64] LINE_REPLY(0x0001208C | 0x8000000F)

[16:30:09:018 - 0x00000620] SetMWI(DestAddress 62790 | State ON) - E_MIU_COLLISION

**Repetitions of these lines***

[03:01:42:007 - 0x000021F8] SetMWI(DestAddress 84083 | State OFF) - E_MIU_COLLISION

[09:43:13:388 - 0x00001520] MakeCall(65259) entered

[09:43:13:388 - 0x00001520] lineMakeCall(65259) - 0x00012385 | New HCALL 0x00000000

[09:43:13:388 - 0x00000E64] LINE_REPLY(0x00012385 | 0x8000001C)

[09:43:13:388 - 0x00001520] WaitFor(0x00012385 | CONNECTED) - 0x8000001C.

CALL SEQUENCE:

. %9

Thanks in advance,

inner_silence