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

Unity 4.1(1) ES 8

Can someone post 4.1(1) ES 8 here or add it to the 4.1.1 Engineering special index page on cisco.com? Hitting bug id CSCsc26421.

4.1(1) Engineering Special index.

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_release_note09186a0080568969.html

4 REPLIES
Cisco Employee

Re: Unity 4.1(1) ES 8

4.1(1)ES8 was a TSP ES build. Those never get published as Unity ESes. Instead, the TSP setup from that build is repackaged into a general TSP ES. That one in particular ended up as 8.1(1)ES1.

The fix you are looking for was also then rolled into the next TSP release, 8.1(2), and of course the more recent 8.1(3) release. Both of these are available for download on cisco.com. I'm not sure why CSCsc26421 didn't show up in the 8.1(2) release notes but I am certian that the fix is in there.

Regards,

Eric

Re: Unity 4.1(1) ES 8

Ok. Yea, we are on 8.1(3) TSP but still seeing this error in the event log exactly as the bug id has.

Cisco Employee

Re: Unity 4.1(1) ES 8

The bug there was that under certian conditions ports would lock and stop answering calls. Hence the first line of the bug release note: "Unity stops accepting calls on affected ports". The fix was to harden the TSP such that it could better handle these conditions, properly clear the port, and immediately be ready to accept the next incoming call.

If you're seeing the event log errors then you are hitting such a condition. If your ports don't get locked up when this happens then the bug fix is working.

In particular, Unity has attempted to answer an incoming call by sending SteationOffHook to CCM. But it seems CCM never fully responds to the offhook request. This is considered an error condition. I don't think there's much else Unity can do with this other than note that the condition has occurred (in the event log), clear the port, and move on with the next call.

-Eric

Re: Unity 4.1(1) ES 8

Ok. Is there any way to get rid of the event log errors or reduce them to warning/informational? Trying to filter out errors for the event log monitoring we do and have seen other errors with same error type for different issues so don't want to filter out on that.

115
Views
0
Helpful
4
Replies
CreatePlease to create content