Has anyone ever noticed whether CDR's are immediately purged from the CDR DB when the records are pushed to a Billing Server? My understanding is the CDR records are maintained according to the CDR Management configuration using the Water Marks and Disk Allocation, and only purged once criteria are metâ¦? All the defaults are set for CDR Mgmt, 3GB Disk Allocation, HWM=80%, LWM=40%... The CDR's should not be purging CDR's that have been delivered to CAR (ART DB) or the Billing Server until the water mark is reached. The CDR database always says no records available (Error Code: 10021) when queried from CAR, CDR->Search, but the Billing Server continues to get records. (as follows)
The reason I am trying to query the CDR DB directly is because a Billing Server only gets records from a PRI circuit receiving local calls, where records for calls received on a CAS-T1 circuit never show up. All calls for both circuits are translated to the same internal DN and take the same internal route path, and the calls always completed successfully, as intended. If the call routing is working as desired, terminating on an internal DN, what the heck is going on with the CDR only creating records for calls from a particular circuit, since they are treated the same once in the system?
Appropriate CDR fields and services have been disabled/re-enabled and restarted, servers also rebooted. No change.
I found a forum that stated to run the following (which I did on the Pub)
- run sql Select max(Error_Record_Id) from car:tbl_error_id_map
- <returned> 209151
- run sql update car:tbl_system_preferences set param_value=209152
- <returned> rows: 26
- restarted CDR Agents, CDR Repository on Pub, Cisco DB Layer Monitors
Still no CDR Records. System set as follows:
CM: 18.104.22.1680-4, Publisher and Subscriber server, all devices registered to Sub
- CDR Enabled Flag=TRUE (Pub and Sub)
- Zero Duration Flag=TRUE (Pub and Sub)
- Call Diagnostics Enabled=FALSE (Pub and Sub)
** we do not want CMR records generated, but we tried to enable this regardless, and no change
- CDR Time Interval=15
(we set this to 1 for testing, so CDR records generate every minute)
When the disk usage exceeds the percentage that you specify and the Disable CDR/CMR Files Deletion Based on HWM check box is unchecked, the system automatically purges all successfully processed CDR and CMR files (those delivered to billing servers and loaded to CAR) beginning with the oldest files to reduce disk usage to the amount that you specify in the Low Water Mark (%) drop-down list box.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...