BUG0392 error

[motox2]

Hey folks, i have been getting alot of these errors below, BUG0392. Anyone have a solution on how to fix these errors for my 7.6 CS1000? Thanks in advance

BUG0392
Zero value in CDR_XFER_TIME. Procedure SETMISCELLANY.

 

[SoftwareRT]

Bug392 is a software registrar error.
Zero value in CDR_XFER_TIME means that the system is encountering a situation where the Call Detail Record (CDR) transfer time value is zero, which is not expected or valid for the SETMISCELLANY procedure.
Procedure SETMISCELLANY is likely handles system parameters, settings, or configurations related to CDR.

Sounds like something changed in your system for CDR settings...

 

[motox2]

any idea on what i should look for? Do you think this could be a route programming issue, or a CDR config issue?

 

[SoftwareRT]

Could be either. Did you make any CDN or Phantom changes before the bugs prints? These types of bugs can be notoriously hard to isolate. Here's how to start narrowing it down:

1. Check how many BUG0392 reports you're seeing.
   If it’s just a few, it might be an edge case. If you're getting a lot, it's likely a systemic issue. possibly tied to a CDN, phantom transfers, or an integration problem.
2. Try manually transferring a call that would hit CDR.
   a. If you get the bug after a manual transfer, the problem could be related to your CDR configuration or data input/output (I/O) handling.
   b. If you don’t get the bug with manual transfers, but still see recurring BUG0392 entries, then it’s likely being triggered by a background process or system-level transfer (like via a CDN or application script).
3. Trap the bug by replicating call scenarios.
   You’ll need to:
   a. Recreate different types of transfers (manual, auto-attendant, CDN-driven, ACD queues, trunk-to-trunk).
   b. Run a trace or enable debug logging during those calls (LD 117 DPRINT ON), if you have it. Don't leave this on, it will overwhelm your buffer.
   c. Check if any scenario results in a zero CDR_XFER_TIME.
4. Identify the trigger.
   Ultimately, you’re trying to either:
   a. Trigger the bug deliberately, so you can observe the conditions,
   b. or monitor enough activity to find the exact call pattern or process that causes it.