Semantix Roaming Components
HomeProductsServicesDownloadsContact UsFAQs
Semantix Roaming Components
Home arrow Products arrow Roaming Components arrow TAP Splitter

TAPSplitter Overview

Splitting a TAP files refers to the process of distributing the calls that are present in a TAP file into two other TAP files. These TAP files will then collectively contain all the calls found in the original TAP file and will have no calls in common between them. In set theory parlance, the set of the two files that are created as a result of the split process constitute a partitioning of the calls found in the original TAP file: their union is the original file and their intersection is the empty set.

Online demo

Click here for an online demo.

Features - Usage

The module's interface is shown below:

Usage: TAP_Splitter <options>
Where mandatory options are:
        -i inputBERfilename
                (input BER filename, containing input TAP data)
        -o outputBERFilename
                (output BER filename, will contain filtered TAP data)
        -f filter.xml
                (filtering specifications)
and optionally:
                When the filtering finishes update AuditControlInfo and make it consistent
                Reverse the filtering logic (output calls NOT obeying the filter)
                output version number
                increase verbosity (you can use it more than once, e.g. -vv)
                this help message

Obviously, the input and output TAP3 filenames must be specified. Equally important, the filtering specification XML file, provided by the "-fs filter.xml" argument dictates how to filter the input file.
Here is a sample XML file:

<?xml version="1.0" encoding="utf-8" ?>
<CallSearchData AndOrOr="AND" FromCallIndex="-1" ToCallIndex="-1">
    <CallType value="MobileOriginatedCall" />
    <CallType value="MobileTerminatedCall" />
    <CallSearchSingleRule FieldTypeName="Charge"  
        FieldVarName="charge" Condition="GT" Value="0" />

This specification file dictates that we want to process all the input calls irrespective of their index, from all those calls we are only interested in Mobile Originated and Mobile Terminated calls, and of these, only those that have at least one instance of "Charge" within them with a value greater than 0.

Integration with Roaming Studio

TAPSplitter performs its work based on a specification given in the filtering XML file. This XML file contains a set of rules that describe the filtering logic. The specifics of the XML format are detailed in the associated documentation, but you don't have to worry about them; Roaming Studio offers an "Export Query to XML" button in the Advanced Call Search:


This allows you to store a query you used and split your files based on it, by feeding them in the TAPSplitter.

You can "glue" this component with a simple script monitoring a directory (perhaps an output directory of your rating engine), and automatically filter out calls that adhere to a specific profile - for whatever reasons (auditing, security, etc). The simple but complete interface allows chaining this module with existing processes and systems or using it in conjunction with other modules to provide more complex solutions for your installation.


    ©2001-2010 Semantix Information Technologies. All rights reserved.
Terms & Conditions        Contact us