
The billing schema describes general billing rules that will be understood throughout the development of the solution
Data collection is executed through the LAN or by FTP. Other protocols for accessing CDR files need to be analyzed case by case and are not supported in this offer.
Files may be collected on regular time intervals that depend on the equipment that generates them and user requirements. The data collection module may be set to poll the source from once per minute to once per day.
The present offer provides support for mediating Nortel GSPv06 files. Other file formats need to be analyzed case by case and are not included in the present offer.
Tasks supported by the mediation module:
All rules need to be expressed 3 weeks at least prior to
implementation
The file uploading process is a DTS service running on the database server. It may be programed to be performed on regular time intervals.
Prior to uploading, the service verifies whether that specific file was already loaded. After loading the file in the to "rate" table, the file is archived in a folder defined by the user.
The rating logic is delivered in the form of a stored procedure on
the database server. Source code is available to the end user and
may be changed at any time by the system administrator or per
request by 4Cmj at an additional charge.
The rating process includes the following tasks:
The trunk ID imposed by the switch would be translated into a more friendly name defined by the end user.
Accounts are identified by the originating trunk group of the call.
Call destination is identified through the analysis of the dialed number. It is assumed that dialed numbers have the following format: XXX CC NSN1. XXX has the same length on a given trunk group and can be stripped if properly setup by the user. The list of possible destinations is account specific.
Each account may have a different tariff table.
Two rating logics are supported:
Important:
A destination discount can be applied during the rating process. The discount can be defined for a specific period of time on selected account sites.
Recurring charges can be set to be invoiced either monthly, quarterly, 2 quarterly or yearly. A label describes the charge.
One time charges are added to the next invoicing run. A label describes the nature of the charge.
The re-rating process is launched by the system administrator according to selection rules depending on the following parameters: Start date*, End Date*, In trunk, Out trunk, Account, Site, Destination.
The recycling process is launched by the system administrator according to selection rules depending on the following parameters: Start Date*, End Date*, ,In Trunk, Out Trunk, Error code.
Call detail discounts to selected regions can be applied within a specified time period. This discount is applied during the rating process and is not dependent on volume.
Volume discounts per destination can defined for each account. The discount can be calculated according to two different methods:
This discount is calculated during the invoicing run.
Growth discounts are applied per destination in comparison to the volume to a specific destination in the previous invoicing run.
Credit notes can be provided as stand alone notes or as line items in the invoice. The label associated with the credit note can be selected from an existing list or added as free text by the end user.
Each invoicing address is associated to an invoicing template that is stored in the database. When launching the invoicing run, the appropriate template is used. The invoicing module supports scripting which gives great flexibility in terms of calculations and presentation.
Output filters are supplied to produce the invoice in pdf, rtf or HTML formats.
*Mandatory parameters