Expected CDRs are not available in the RatedCDR table in Billing Reports and in CDRAnalyzer. The “CDR is skipped” warn message is logged in CDR rate log file.
2014-05-25 13:20:49|CDRRate |WARN |CDR is skipped, TransactionId = 0, CallId = ejloRzR1Mi4yMjA=, Product = Gold, Customer = XYZ, Customer Device = XYZ-sbc / 10.29.118.21, Provider = Telcom, Provider Device = 192.168.134.74 / 192.168.134.74
A review of the CDR Rate log messages will show warning messages that a CDR has been skipped by the rating process.
In the NexOSS database, CDRs are stored in the REACDR table until they are rated and moved to the RatedCDR table. CDRs in the REACDR table are rated twice, once using the Product or Customer rate to determine what the customer owes, and second time using the Provider rate to determine what is owed to the provider. If Product, Customer, or Provider rates are not available to rate the call, the CDR will be skipped. The CDRs “Updatable” status will remain S (Skipped) until it is manually reset to Y (Yes). Only CDRs with Updatable=Y in the REACDR table will be rated.
In this example, a rate plan is missing for the Gold Product, Customer XYZ or Provider Telcom.
The solution is to provision the missing rate plan and then change the CDRs updateable status from ’S’ to ‘Y’. To do this, connect to the database and change the Updatable status in the REACDR table from ’S’ to ‘Y’ using the following example.
[ossadmin@dialer-oss LOG]$ sqlplus appiaoss/ossappia@dbdialer SQL*Plus: Release 18.104.22.168.0 Production on Wed Mar 19 14:11:35 2014 Copyright (c) 1982, 2009, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 22.214.171.124.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> SQL> update REACDR set updatable = 'Y' where updatable ='S'; SQL> commit;
If rates are available for the CDRs, they will be rated the next time the CDR-Rate process runs.