CSCsq76303

Unanswered Question
Sep 25th, 2008

Anyone happen to have an update on when, if this bug will be fixed or there is an ES we can apply?

It says its fixed in the bug toolkit:

Workaround:

In order to recover any locked ports, the Unity server needs to be rebooted.

This defect has been fixed in the following engineering specials:

Cisco Unity 5.0(1)ES48 or later

Cisco Unity 7.0(2)ES1 or later.

However, TAC is saying they are seeing cases were its not fixed, even afer applying those ES's. TAC SR# is - 609670547.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Christopher McAlpin Thu, 09/25/2008 - 12:01

A fix for this defect is included in the latest 5.0(1) and 7.0(2)ES. As Unity 4.2(1) and higer ES's are now cumalative (for the most part), the actual ES number may change.

adignan Thu, 09/25/2008 - 12:02

It says its fixed in the bug toolkit:

Workaround:

In order to recover any locked ports, the Unity server needs to be rebooted.

This defect has been fixed in the following engineering specials:

Cisco Unity 5.0(1)ES48 or later

Cisco Unity 7.0(2)ES1 or later.

However, TAC is saying they are seeing cases were its not fixed, even afer applying those ES's. TAC SR# is - 609670547.

Christopher McAlpin Thu, 09/25/2008 - 12:08

Oh, I do apologize. TAC has re-opened the defect as it appears the fix did not resolve the probem as you noted. I personally have no ETA. TAC will have to work with development to obtain a status.

Actions

This Discussion