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.
...
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.
...
| 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 | ||
|---|---|---|
| ||
In this Example our Business Log for associating a CDR record (call) to a Customer was based on the [Calling Number] matching our Customers Caller-ID 647 865 5000 If the [Calling Number] is equal to 647 865 5000 then we will assume the call was made by that Customer and charge the call to the Customer. SOLUTION #1
Authentication defined on Customer A/C using [Calling Number] field (click to display) Notice that because we are writing the matching expression in Regular Expression notation we write the telephone number enclosed in parentheses. This is the way to write a Regular Expression markup for matching a complete string, so we are saying the call should be charged to this customer if and only if the [Calling Number] field matches the entire string between the parentheses (6478655000) SOLUTION #2 You will notice that in the Brekeke CDR file the callers number is represented in SIP URI notation, i.e. However in Option #1 we were able to use the CDR2Cloud filed called [Calling Number]. This is because the CDR2Cloud system reads the Brekeke CDR files [from-uri] field and converts it from SIP Notation to a simple number format and places it in a CDR2Cloud field called [Calling Number]. This allowed us to ignore the [from-uri] and work with the [Calling Number] field. We could have used the [from-uri] field directly but it would require us to write a slightly more complicated Regular Expression as we now have to evaluate the name part of the SIP URI
Authentication defined on Customer A/C using [fromUri] field (click to display) |
...