cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
715
Views
0
Helpful
2
Replies

Port locked but, showing idle

slc2
Level 1
Level 1

UM 4.04sr1, e2k

I have the following error:

Event Type: Warning

Event Source: CiscoUnity_Miu

Event Category: Warning

Event ID: 584

Date: 2/10/2005

Time: 2:06:29 PM

Description:

Port 4 has been busy since 2005-02-04 11:08:34. The system threshold is 240 minutes, indicating that this port is currently unavailable and may be unable to handle further calls.

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

===========

Tried calling that port and it does not answer. Port Monitor (web and exe) show the port idle. Looks like a bug since it incorrectly shows the status of the port. Not able to reset the port either. This is an incoming call port only.

No errors show up after trying out the reset.

Sabas

2 Replies 2

mrmccann
Cisco Employee
Cisco Employee

Although the port appears idle, it is apparently busy as far as Unity is concerned, which is why it won't answer calls. The warning you see is just an indicator to let you know there is a port that isn't functioning properly. It also gives you a timeframe for when the problem occurred that originally caused this problem - around 2/4 at 11:08. If you look back in your event log, you may see some errors on Port 4 around this time or earlier that could give some more clues as to what the root cause was.

You didn't by chance have any diagnostic traces on, did you? Also, what type of phone system are you integrating with?

The only sure way to get this port working right again is to restart the server.

Two issues. One, why did it lock, Second, why is it showing idle when in fact is not responding.

Intecom E14 pbx

Event Source: CiscoUnity_Wav

Event Category: Error

Event ID: 805

Date: 2/4/2005

Time: 11:08:34 AM

Description:

Cisco Unity's multi-media component has enountered a serious error.

EXPLANATION:

A serious failure has occurred on port 4 while reading data from an audio stream. Depending upon the severity of the failure, parties on this call could experience unexpected behavior or be disconnected. In some cases, further calls on this port will not be handled correctly.

TECHNICAL DETAILS:

Thread 0x00000EE4 had a Failure on Port 4 in AvWav

DESCRIPTION:

File: e:\views\cs_ue4.0.3.159\un_Miu\UnityAvWav\STRMIO.CPP(217)

Method: StreamIoRead

Failure: call to IStream:Read with error(80040115).

Event Source: CiscoUnity_Wav

Event Category: Error

Event ID: 801

Date: 2/4/2005

Time: 11:08:34 AM

Description:

Cisco Unity's multi-media component has enountered a serious error.

EXPLANATION:

A serious failure has occurred on port 4 during wav media processing. Depending upon the severity of the failure, parties on this call could experience unexpected behavior or be disconnected. In some cases, further calls on this port will not be handled correctly.

TECHNICAL DETAILS:

Thread 0x00000EE4 had a Failure on Port 4 in AvWav

DESCRIPTION:

File: e:\views\cs_ue4.0.3.159\un_Miu\UnityAvWav\WAV.C(4548)

Method: WavReadFormatPlay

Failure: call to WavRead failed.

Event Source: CiscoUnity_ConvSubscriber

Event Category: Error

Event ID: 119

Time: 11:08:34 AM

Description:

An unexpected error has occured while a subscriber is on the phone with Unity. This can potentially result in the subscriber hearing the failsafe conversation. Technical details are - IAvDohMailUser::get_Inbox returned [0x8004000c] on line 895 of file e:\views\cs_ue4.0.3.159\un_Conv1\AvConvSubscriber\AvConvSubMsgCountSvr\AvSCOSAndMsgCount.cpp.

No, specific traces running at the time.

These are the only entries in the Diag_AvCsMgr log

11:08:07:226,AvDiagnostics_MC,1142,3844,3,0BE507FF6D274FD69B3C855DEF38BB1B,-1,-1

11:08:34:711,AvDiagnostics_MC,2161,3812,4,DE3F4E1D2B5A409A88F3B428A98CFBD8,MiuGeneral,0,4, File: e:\views\cs_ue4.0.3.159\un_Miu\UnityAvWav\STRMIO.CPP(217) Method: StreamIoRead Failure: call to IStream:Read with error(80040115),0x00000EE4

11:08:34:712,CiscoUnity_Wav,805,3812,4,DE3F4E1D2B5A409A88F3B428A98CFBD8,-1,-1,4,0x00000EE4,4, File: e:\views\cs_ue4.0.3.159\un_Miu\UnityAvWav\STRMIO.CPP(217) Method: StreamIoRead Failure: call to IStream:Read with error(80040115)

11:08:34:711,AvDiagnostics_MC,2161,3812,4,DE3F4E1D2B5A409A88F3B428A98CFBD8,MiuGeneral,0,4, File: e:\views\cs_ue4.0.3.159\un_Miu\UnityAvWav\STRMIO.CPP(219) Method: StreamIoRead Failure: call to IStream:Read bytes read(4000),0x00000EE4

11:08:34:712,CiscoUnity_Wav,805,3812,4,DE3F4E1D2B5A409A88F3B428A98CFBD8,-1,-1,4,0x00000EE4,4, File: e:\views\cs_ue4.0.3.159\un_Miu\UnityAvWav\STRMIO.CPP(219) Method: StreamIoRead Failure: call to IStream:Read bytes read(4000)

11:08:34:711,AvDiagnostics_MC,2161,3812,4,DE3F4E1D2B5A409A88F3B428A98CFBD8,MiuGeneral,0,4, File: e:\views\cs_ue4.0.3.159\un_Miu\UnityAvWav\WAV.C(2360) Method: WavRead Failure: call to mmioRead failed,0x00000EE4

......

.

.

11:08:34:836,CiscoUnity_ConvSubscriber,119,3812,4,DE3F4E1D2B5A409A88F3B428A98CFBD8,-1,-1,IAvDohMessageIterator::SetFilter,0x80040115,3292,e:\views\cs_ue4.0.3.159\un_Conv1\AvConvSubscriber\AvConvSubMsgStackSvr\AvSPlayMessageStack.cpp

11:08:34:837,CiscoUnity_ConvMsg,10001,3812,4,DE3F4E1D2B5A409A88F3B428A98CFBD8,-1,-1,Running conversation SubMenu on Port 4 Running conversation SubNewMsgStack on Port 4

11:08:34:867,CiscoUnity_ConvSubscriber,119,3848,5,1DC11EC9DD2040AC8C02A9D3F3795681,-1,-1,IAvDohMailUser::get_Inbox,0x8004000c,895,e:\views\cs_ue4.0.3.159\un_Conv1\AvConvSubscriber\AvConvSubMsgCountSvr\AvSCOSAndMsgCount.cpp