Field Notice: FN74340 - Call Center Event Recording File-Handling Issue After Upgrading Cisco BroadWorks Application Server to Java 11 (Releases 2025.07–2025.09) - Software Upgrade Recommended

Available Languages

Updated:November 17, 2025
Document ID:FN74340

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

High
Impact Rating:
High
First Published:
2025-Nov-17
Last Published:
2025-Nov-17
Revision:
1.0
Cisco Bug IDs:

Notice

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

Products Affected


Affected Software Product Affected Release Affected Release Number Comments
Base Software RI RI.2025.07, RI.2025.08, RI.2025.09  

Defect Information


Defect IDHeadline
CSCwr81750Issues with ccEventRecording after upgrade

Problem Description


When upgrading Cisco BroadWorks Application Server (AS) to Release RI.2025.07 or later, up to Release RI.2025.09, Call Center Event Recording (CCER) activity files are not processed as expected. These files remain in the pendingTransfer directory for one day and are deleted the following day, which can result in data loss.


Background


This issue is caused by improper handling of internal data exposed by the higher precision timestamp that is associated with Java 11. As a result, the initial activity file that is generated after the upgrade prevents subsequent files from being processed until it is deleted. After this problematic file is removed, files that are generated on subsequent days are processed normally. The issue will not recur unless Cisco BroadWorks AS is restarted or the CCER configuration is updated. However, restarting Cisco BroadWorks AS or updating the CCER configuration (through AS_CLI > Interface > CallCenterEventRecording) may trigger the problem again.


Problem Symptom


CCER activity files remain in the pendingTransfer directory for one day and are deleted the next day without being processed. There is a risk of losing Call Center activity files for one day, with normal processing resuming after the initial problematic file is removed. The issue may recur if Cisco BroadWorks AS is restarted or if the CCER configuration is modified.


Workaround/Solution


Workaround

There is currently no workaround for this issue.

Solution

Cisco recommends not restarting Cisco BroadWorks AS or updating the CCER configuration until the fixed release is applied. The issue has been resolved in Cisco BroadWorks AS build 2025.10, which is now available from the Cisco Software Download Center.


Revision History


VersionDescriptionSectionDate
1.0Initial Release—2025-NOV-17

For More Information

For further assistance or for more information about this field notice, contact the Cisco Technical Assistance Center (TAC) using one of the following methods:

Receive Email Notification About New Field Notices

To receive email updates about Field Notices (reliability and safety issues), Security Advisories (network security issues), and end-of-life announcements for specific Cisco products, set up a profile in My Notifications.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products