Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

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

Problems with Unity 3.04

I am having the following problems with unity;

AvCiscoTsp device 11: Disconnected from CallManager

Component Miu: Thread 0x00000E44 had a Failure on Port 7 in Method CAvTSPAbstraction::Selsius_SetMWI()

DESCRIPTION: HardFailure from lineDevSpecific.


DestAddress: 2420

Messages: 1

State: ON

ErrorCode: 0x80000048.

My question is whether this is a known problem to the 3.0 code, configuration or more than likely something else.


Cisco Employee

Re: Problems with Unity 3.04

For that first issue, we'd need to look at the entire Unity system at the time of the TSP disconnect to determine if this is a pervasive problem, or just normal behavior. Having a disconnect happen every so often is not a problem. However, if you see multiple disconnects from multiple ports at the same time (especially if you see the ports "looping" that is, disconnecting, re-connecting disconnecting reconnecting...), that's a problem. It's not a problem of the TSP; it's a sign things elsewhere in Unity aren't responding in a timely manner.

For the MWI, that's probably not a defect. That error message is what you'll get when the AvSkinnyTSP thought that the MWI request mechanism at the Skinny layer did not work. This could be that the TSP got a skinny event back from CCM that it wasn't expecting, or it didn't get the event at all. For the TSP to consider the MWI request to be successful (and return a success code instead of 0x80000048), it has to get a specific skinny message from CCM.

Is that happening a lot? Intermittently? Always? If it's always happening, set the AvSkinnyTsp traces and reproduce a MWI attempt. If you post the traces, we can take a look.

CreatePlease login to create content