This walkthrough provides an introduction to CDR2Cloud Authentication Code (Auth Code) feature and how to effectively use Auth Codes to identify which customer CDR calls should be billed to.
This walkthrough will cover the following steps:
- Anatomy of a CDR file
- Business Logic for Identifying Customers
- Define Authentication (Auth) Code for Customer Records
| Anchor | ||||
|---|---|---|---|---|
|
CDR files come in many different formats, sizes and field definition. Every PBX manufacturer has a different CDR file format, however we can safely say that every PBX produces a CDR file. CDR files are basically log files that contain a transaction record of calls that have been processed by your PBX, SIP Server or Network. When operating a PBX there are basically 2 accepted ways of producing billing records, RADIUS and CDR files. CDR2Cloud allows you to easily produce billing records from your CDR files by reading each line in the CDR file and bill that line to a customer. You must however define the logic that will be used to associate that line from the CDR file to a customer, but you must first understand what data is in your CDR file and how it relates to your customer.
...
CDR File in EditPad Text Editor (click to display)
CDR File in Microsoft Excel (click to display)
Notice that there are 9 records (rows) with 9 fields (columns). If viewed in a Text Editor you will notice that each field is separated (delimited) by commas, however when viewed in Excel the columns are more clearly marked. We have added the column header descriptions to the Excel image for the purpose of this walkthrough. Your CDR file may have a few or thousand rows, however we are more interested in the fields (columns) as they hold the key to determining which customer the call should be billed to.
...
| how long did the call last for | 3 seconds |
|---|---|
| when did the call start | 12:41 GMT |
| what phone number was called | 12896980000 |
CDR File in Microsoft Excel (click to display)
We must now figure out how each field (column) relates back toy our customer that we would like to charge the call to. We will do this in the next section Business Logic for Identifying Customer Calls.
| Anchor | ||||
|---|---|---|---|---|
|
Now that we have a clear understanding of the fields in our CDR file we can take a look at how we will determine the Business Logic that is needed to identify each CDR record to a customer.
...
| Panel | ||
|---|---|---|
| ||
We will use the [Calling Number] to identity our customers calls. This means that if the [Calling Number] matches our Customers Caller-ID then we will assume the call was made by that Customer and therefore charge the call to the Customer. Our Customer John Doe makes calls from his mobile phone 647 865 5000, as such any record in our CDR file with the [Calling Number] = 647 865 5000 will be identified to John Doe. Taking a look at the CDR file extract (see image below), we can see that there are 2 calls that should be charged to John Doe based on our Business Logic. |
| Panel | ||
|---|---|---|
| ||
We will use the [Called Number] to identity our customers calls. This means that if the [Called Number] matches a specific number then we will assume the call was made by that Customer and therefore charge the call to the Customer. Our Customer John Doe makes calls to mobile phone 905 200 5998, as such any record in our CDR file with the [Called Number] = 905 200 5998 will be identified to John Doe. Taking a look at the CDR file extract (see image below), we can see that there are 4 calls that should be charged to John Doe based on our Business Logic.
|
| Panel | ||
|---|---|---|
| ||
We will use the [Source IP Address] to identity our customers calls. This means that if the Source IP Address] matches a specific IP Address then we will assume the call was made by that Customer and therefore charge the call to the Customer. Our Customer John Doe makes calls from his network which has a source IP Address of 60.20102.106, as such any record in our CDR file with an IP Address of 60.20102.106 will be identified to John Doe. Taking a look at the CDR file extract (see image below), we can see that there are 5 calls that should be charged to John Doe based on our Business Logic. |
| Anchor | ||||
|---|---|---|---|---|
|
Now that we understand the anatomy of CDR file and have defined our business logic for linking calls to our Customers, the last thing we have to do is convert this Logic into a format that the CDR2Cloud will understand.
...
| Panel | ||
|---|---|---|
| ||
In this Example our Business Logic for associating a CDR record (call) to a Customer was based on the [Source IP Address] matching our Customers IP. If the [Source IP Address] is equal to 60.20102.106 then we will assume the call was made by that Customer and charge the call to the Customer. You will notice that in the Brekeke CDR file the [from-uri] field is represented in SIP URI notation, i.e. We must instruct CDR2Cloud to check the IP Address of the [from-uri] for each record and compare it to the IP Address that we will define for the customer
Authentication defined on Customer A/C using [fromUri] field (click to display) |
[fromURI] = sip:.+@(
Related articles
| Filter by label (Content by label) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|