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

Conversation AMIS Error.

UM 3.15, E2k, W2k, Intecom switch.

I am getting three or so of these AMIS errors through out the day. They keep referencing back to port 3. However, we are not using AMIS networking. We are using the Octel Bridge.

Anything to look at?

Sabas Chois

Event Type: Error

Event Source: AvConvMsg_MC

Event Category: Error

Event ID: 10002

Description:

IAvMiuCallr::GatherDigits returned [0x80040102] on line 126 of file e:\views\cs_UE3.1.4.39\un_Conv3\AvConvAmis\AvConvAmisInbound\AvSAIStartFrame.cpp

Running conversation ConvAmisInbound on Port 3

Notes: All Cisco Unity Errors

1 ACCEPTED SOLUTION

Accepted Solutions
New Member

Re: Conversation AMIS Error.

So this error was logged for the AMIS Inbound conversation, meaning that someone else is calling into the Unity system. Either one of two things is likely happening:

1) Some other Voicemail system is trying to send you an AMIS message, and is in error.

2) Some other Octel system is trying to send you a message, when it should be dialing the Cisco Unity Bridge server instead.

I'm guessing the problem is #2 (since an Octel System would initiate an Octel Analog Networking session much like an AMIS session with a 'CD' packet instead of just a 'C' packet, Unity mistakenly confuses this as AMIS, can't handle the incorrect AMIS frame, and logs the error).

Make sure that all of your Octel systems are configured to dial the Cisco Unity Bridge server when it delivers messages, not to dial the Cisco Unity server itself.

Hope that helps.

-Robert

1 REPLY
New Member

Re: Conversation AMIS Error.

So this error was logged for the AMIS Inbound conversation, meaning that someone else is calling into the Unity system. Either one of two things is likely happening:

1) Some other Voicemail system is trying to send you an AMIS message, and is in error.

2) Some other Octel system is trying to send you a message, when it should be dialing the Cisco Unity Bridge server instead.

I'm guessing the problem is #2 (since an Octel System would initiate an Octel Analog Networking session much like an AMIS session with a 'CD' packet instead of just a 'C' packet, Unity mistakenly confuses this as AMIS, can't handle the incorrect AMIS frame, and logs the error).

Make sure that all of your Octel systems are configured to dial the Cisco Unity Bridge server when it delivers messages, not to dial the Cisco Unity server itself.

Hope that helps.

-Robert

99
Views
0
Helpful
1
Replies
CreatePlease login to create content