[cisco-voip] Unity 4.0(5) and CME MWI issues

[Erick Bergquist]

Pat,

Thanks. Will give the workaround a try tomorrow.

Do you know if the following is all that is needed for MWI on CME when
integrated with regular Unity?

ephone-dn  66
 number 1099 secondary 1098
 mwi on-off

or is it the way below, because they had this in there to but I found
above method on cisco,com for use with regular Unity.

ephone-dn  68
 number 1098....
 mwi off

ephone-dn  69
 number 1099....
 mwi on

In the AvScMgr trace, I see MWI dial out on same port a couple times
in same timestamp.

In the AvNotiferMgr log, I see this NO RESOURCE over and over again..

15:50:47:640,AvDiagnostics_MC,642,5764,-1,,Notifier,12,m_pMWIDevice->GetArbiter()->SetMWI(4708
| ) returned [0x80041C00; E_ARBITER_NO_RESOURCE]

On Nov 26, 2007 8:08 PM, Pat Hayes <pat-cv at wcyv.com> wrote:
>
> http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCse97325
>
>
>
> -------- Original Message  --------
> From: "Erick Bergquist" <erickbee at gmail.com>
> To: "Cisco Voip Mailing list" <cisco-voip at puck.nether.net>
> Subject: [cisco-voip] Unity 4.0(5) and CME MWI issues
> Date: 11/26/2007 8:51 PM
>
> > Hello,
> >
> > Has anyone done a regular Unity integration with a CME before?
> >
> > Have Unity 4.0(5) with Unity TSP version 8.2(1)  going to a CME 4.1
> > system (12.4(15)T1) and MWI works, but the Unity servrer is getting
> > the constant warning in the event logs every few seconds and it
> > causing high CPU usage upwards of 40 to 50% all the time on the
> > AvCsMgr service.The Unity AvCsMgr diagnostic log file is full of MWI
> > attempts, and in the AvNotifer diag log file it has MWI attempts to
> > and always saying NO RESOURCE as reason code.
> >
> > Server and router have been rebooted (before I got involved in this)
> > and did not help. Users are not complaining of MWI issues, and the
> > extensions in these warnings exist on the router and the phones work
> > fine.
> >
> > I got a TAC Case open also ..
> >
> >
> > Event Type:   Information
> > Event Source: CiscoUnity_TSP
> > Event Category:    None
> > Event ID: 127
> > Date:         11/21/2007
> > Time:         2:55:21 PM
> > User:         N/A
> > Computer: UNITY
> >
> > Description:
> >
> > Cisco Unity-CM TSP device 15 (Cisco Unity port 11): An attempt to turn
> > ON the message waiting indicator (MWI) for extension 4821 failed
> > because a collision occurred with an incoming call on the same port.
> >
> >  The MWI request will be retried. But to prevent collisions, we
> > recommend that ports setting MWIs be isolated from ports handling
> > incoming calls. If the MWI status remains unchanged for an extended
> > period of time or if there are many of these warnings from Cisco Unity
> > in a short period of time, there may be an MWI misconfiguration or
> > another problem.
> >
> > For more information, refer to the "Message Waiting Indicators"
> > chapter in the Cisco Unity Troubleshooting Guide.
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
>