Call Processing Made Simple

Wednesday, 07. 1. 2009  –  Category: Ranger Wireless Solutions

Call processing systems can simply be divided into two major functions, which can be described characteristically as front-end and back-end processes. By and large, call processing consists of steps that are associated with the routing and control of a call. Typical call processing is contingent upon a telephony switch that contains vendor-specific elements specialized to routing of a call, and stamps certain call detail field records with pertinent caller subscriber data to provide the call detail record with additional call intelligence for billing and reporting.

Most call processing systems employ the front-end process to retrieve and receive call detail records from a specific source. The process can then optionally reformat and edit the call detail records and assigns carrier account information to the call detail records to pre-dispose them to further intelligence for back-end call processing.

Back-end processes consist primarily of billing and reporting functions. Most back-end and invoicing processes will most sensibly and assuredly be contained and invoked via some type of configuration, vis-à-vis a web portal or menu structure.

Front-end and back-end call processing systems will contain many database tables of information. Some of the key database tables hold carrier (customer) information, call detail records, rate tables, and billing records that are ready to be invoiced. For example, a customer database table holds unique identification information about a carrier. A call detail record database table holds all calls and their associated detail. A rating database table holds the rate plan identifier codes and charges associated with each carrier’s rate plan. The billing database table holds the call detail billing records.

Front-End Call Processing
In an automated (batch) or manual function, and in a pre-determined time frame, a front-end process seeks out the latest call detail records from a telephony switch and stores them away on the front- and back-end call processing host system. The front-end process could also evaluate the calls to 1) determine if the call is billable and 2) perform certain lookups to add pertinent information to the call detail record for billing and reporting functions and 3) to add each call detail record to various reporting and billing database tables where it is ready to be invoiced and reported on. Front-end processing could also consist of utility functions (i.e., removing duplicate call detail records) and nightly summarization of call detail records for reporting purposes.

Back-End Call Processing
Back-end process is very specific to billing. There should exist management billing reports that can be initiated to report on the call detail records regardless of their state of invoicing.

As described above, a function of the front-end process is to create a database table or “pool” of un-rated call detail billing records. This pool contains billing records that are ready for invoicing but have not yet had rates assigned to them. Separate rating database tables exist to apply charges to these billing records in the process of invoicing. Each carrier could have unique rates and charges. Charge calculations are contingent upon the type of call. For example, a “Completed Call” charge calculation is determined by rating calls by volume and duration. Other types of calls could be rated based upon only volume (not duration).

Back-end invoice processing consists of gathering of carrier billing records, and using the rating tables to assign charges to them. These billing records with their associated rates are then stored in separate invoicing summarization tables where the invoice data is then extracted from. Once the invoicing process is complete, there are management billing reports that can be run to review the invoices and invoiced and non-invoiced billing records.

Steve Soltys works for RANGER Wireless Solutions, a CornerWorld company.

Tags: billing, billing records, call processing, Steve Soltys