Admin: Created page with "This window summarizes the activity of the switches, the distribution of calls by type, the routes with any billing trouble, and the detail of CDR files mediated between the s..."

2013-07-31T16:24:44Z

Created page with "This window summarizes the activity of the switches, the distribution of calls by type, the routes with any billing trouble, and the detail of CDR files mediated between the s..."

New page

This window summarizes the activity of the switches, the distribution of calls by type, the routes with any billing trouble, and the detail of CDR files mediated between the switches and the BILLING module.

The displayed data corresponds, by default, to the information of the previous day. You can customize your search by date, using the field âFromâ of Figure 36. Or use the < and > to move one day forward and one day backward.

<center>[[Image:Figure36billing.gif]]</center>

<center>''Figure 36. Search by Date Window.''</center>

'''Summary'''

The first table of the summary represents the number of files mediated between the BILLING module and the Switches.

The red cell denotes that the system has mediated fewer files than it should have.

<center>[[Image:Figure37billing.png]]</center>

<center>''Figure 37. Summary.''</center>

'''Call Type'''

The second part of the table in the Summary window is Call Type. Following is a description of the fields of this table.

Table 1. Call Type Definition

Call Type & Description

Mediated -- This field refers to the amount of calls in terms of sets of messages (2 or more) comprising a call.
Connected -- A call is successfully connected when thereâs a ringing tone or the call is answered. A connected call is also a call that has to be billed
Accepted -- A call that has been mediated successfully.
Access
Damaged -- The register has been corrupted and the call cannot be billed.
Not Rated -- Calls that have not been rated by the BILLING module.
Stuck -- These are calls which duration exceeds the configured length limit in the system.
Errors
Successfully Billed -- The number of accepted calls that have been billed by the platform minus the stuck calls.
Billed Calls Should Be -- The number of connected calls that should be billed by the platform minus the stuck calls.

âSuccessfully Billedâ and âBilled calls Should Beâ numbers should match. A red cell denotes a problem if they donât.

The second table in the screen summarizes the billing problems for the prior day. First, you will find the billing codification (figure 38) and then the details of the events per route (figure 39).

<center>[[Image:Figure38billing.png]]</center>

<center>''Figure 38. Billing Codes and Table of Events.''</center>

The following table explains the meaning of the billing codes.

Table 2. Billing Codes Description

Billing Code & Description

Not Rated -- The call has not been rated due to some error in the processing.
Rated -- The call is billed. If there are errors in the process, the other indicators will clarify.
Default Rate -- Calls billed with a default configurable rate.
Hourly -- The call is billed by the normal process that runs every hour after every mediation.
No Clientâs Rate -- The clientâs rate does not exist in the rate registry. The system bills using the default rate.
No Providerâs Rate -- The providerâs rate does not exist in the registry. The system bills using the default rate.
Fixed -- This indicator denotes that there were damaged calls that were fixed and billed.
Stuck Call -- These are calls which duration exceeds the configurable length limit. These calls are not billed.
Not Billed Call -- Calls that could not be billed by the system.

The billing unusual events for the prior day are summarized in the following figure. It makes use of the billing codes to explain the nature of the event.

<center>[[Image:Figure39billing.png]]</center>

<center>''Figure 39. Routes Presenting Billing Problems.''</center>

The following table describes the heading fields of the billing events summary.

Table 3. Billing Events - Parameters

Field & Description

Code -- This is the internal code for the carrier.
Client -- This is the actual customer sending traffic to a destination through your switches.
Org_sub -- Clientâs identity that sends the call.
Provider -- Providerâs identity that terminates the call.
Dst_sub -- Destination providerâs identity that terminates the call.
Tg_in -- This indicates the trunk group of the customer.
Tg_out -- This indicates the trunk group of the provider.
Cld Called_id. -- This is the called party number.

'''Calls Without Subscription'''

These are the calls that cannot be associated to a customer or provider.

<center>[[Image:Figure40billing.png]]</center>

<center>''Figure 40. Calls Without Subscription.''</center>

The field CIng refers to the calling party number.

'''Detail by File'''

This table contains details of the CDR files collected by the Agents and mediated in the platform.

<center>[[Image:Figure41billing.png]]</center>
Figure 41. Detail by File.

The following table explains the fields of the Detail by File window.

Table 4. Details of the Mediated Files.

Parameter & Description

Agent -- Switch where the CDR are collected.
Description -- Name of the CDR file. The format contains the location, date and time.
Mediated -- Files mediated by the BILLING module.
Connected -- Connected calls.
Accepted -- Accepted calls.
Damaged -- The file has been corrupted and cannot be processed.
Access
Damaged

Billing Mediation - Revision history

Admin: Created page with "This window summarizes the activity of the switches, the distribution of calls by type, the routes with any billing trouble, and the detail of CDR files mediated between the s..."