CDR Preprocessing

CDRs may be generated from a multitude of sources resulting in a variety of formats. As such CDRs are preprocessed and loaded into the cdr table before being associated to a Package/Service and before being rated. Making preprocessing easily modifiable supports billing outside the NANPA domain.

Preprocessing is done via a program or scripts that output CDRs in a format expected by BillMax. Preprocessing scripts are located in /usr/local/billmax/local and the file name is pre-pended with string preprocesscdr_. The following CDR formats are supported by default:
  • Asterisk®
  • PBXWare®
  • Frontier®
  • NetSapiens® Advanced
  • Voyant® EMI CDRs.
These formats are itemized in the List cdrsources.
You add processing of a CDR format by adding a CDR Source and specify the CDR format. The CDR Source also specifies how CDRs are to be classified:
No
CDRs are not classified with respect to USF and will not be.
Use NPANXX Table
Classify the CDRs for USF purposes using the NPANXX tables.
Pre Classified
The CDRs are pre classified for USF purposes.
The CDR Source also specifies how CDRs are to be rated:
No
CDRs are not to be rated. By definition this means CDRs will be associated but not billed in any way. Use this if you want to capture CDRs for informational purposes such as traffic studies.
Yes
Rate the CDRs according to the CDR Billing Plan.
Pre Rated
CDRs are pre rated and the amounts are submitted with the CDRs.
The CDR preprocessing script is responsible for the following:
  1. Eliminating calls that should not be considered such as those never connected.
  2. Removing non-numeric characters from the from the source and destination numbers.
  3. Eliminating calls from consideration based on length of number dialed or other considerations such as number being a long internal extension.
  4. Flagging N11, international call, Operator assisted calls, Toll Free calls and Premium calls as such. In addition, if needed, flagging calls as Local calls.
  5. Outputting the necessary source, destination and Rate Deck keys to match Package/Service d01 values and values in the Rate Decks.
  6. Depending on the source of the CDRs, the CDRs may be tagged as inbound, outbound or indeterminate. If indeterminate and the source is in BillMax it is considered outbound. If indeterminate and the destination is in BillMax, it is considered inbound. If indeterminate and both the source and destination numbers are in BillMax, it is considered both inbound and outbound and a additional CDR for the inbound portion is created.

The output format from CDR preprocessing may be found here BillMax CDR Input Format.