Guest

Cisco Unity

Field Notice: *Expired* FN - 14014 - D120JCT - Unity Sees Second Call Appearance 1000ms After Disconnect


Revised October 13, 2006

June 27, 2001

NOTICE

THIS FIELD NOTICE HAS BEEN ARCHIVED AND IS NO LONGER MAINTAINED OR UPDATED BY CISCO.

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE, WARRANTY OR SUPPORT. USE OF THE INFORMATION ON THIS FIELD NOTICE OR MATERIALS LINKED FROM THIS FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Product

Top Assembly

Printed Circuit Assembly

Comments

HW Rev.

Part Number

Rev.

Part Number

Rev.

UNITY-D/120JCTLS

74-2265-01

-A0

   

Dialogic Voice Boards for PBX integrations, sold and supported by Active Voice. Now Cisco sold and supported.

 

ECS-D/120JCTLS=

74-2489-01

-A0

   

Dialogic Voice Board spare

 

Problem Description

There have been two reported cases (CSCae06158) of customer sites using D/120JCT-LS and D/120JCT-EURO Dialogic boards, having a problem with Cisco Unity seeing a second call appearance 1000ms after disconnect.

Background

Intermittently, the D/120JCT firmware falsely detects energy present after going from an off-hook to an on-hook state and detects this as a valid ring signal. The occurrence and frequency of the problem depends on the level of the ring signal and the phase of the ring signal coming from the private branch exchange (PBX).

For the D/120JCT-LS board, Dialogic resolved this problem and another problem related to Japan Caller ID failures with both a firmware modification (SR 5.00 or later) and a hardware modification (board revision 99-3931-207). The firmware modification resolves the false ring detect problem. For the EURO board, Dialogic is not planning on modifying the hardware since the firmware modification resolves the false ring event problem.

Cisco Engineering has not tested or qualified the modified Dialogic boards (SR 5.00 or later), and recommends using the workaround to address the problem symptoms (see Work Around/Solution below).

Problem Symptoms

After a caller hangs up, the port goes idle for one second. A subsequent call appears on the same port, but it is a phantom call. The port remains occupied until the conversation times out due to no caller response.

Workaround/Solution

Cisco Engineering has not tested or qualified the modified version of the Dialogic boards, and recommends using the workaround provided here:

Increase the MinimumRingOnInterval setting in the switch file from the default setting of 200ms to 500 ms or higher.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCae06158

Detail: On the D120JCT system on which we had been testing, on many ports, if you called into voice mail, then hung up, in TapiBrowser and StatusMonitor you could see the port go idle, then another call appearance on the same port 1000ms later even though there was really no call. The port would stay occupied until it timed out on the conversation because of no caller response.

How To Identify Hardware Levels

D/120JCT-LS

===========

To identify the revision of the D/120JCT-LS voice board, you must shut down the system, remove the voice board from the server, and find the top level part number and revision.

D/120JCT-EURO

=============

All revisions of D/120JCT-EURO voice board are affected. There is no need to identify the revision.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.