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


This module validates a TAP file according to the applicable TD.57 standard. All TAP3 releases are supported (TAP3.1 up to TAP3.11 as of October, 2010).

Online demo

Click here for an online demo.

Features - Usage

The module's interface is shown below:

Usage: TAP_Validator <options>
where options must include:
        -i   inputTapFileName
and optionally, any of:
        -o createdTapFileName
                TAP file containing non severely errored calls
                Save original call indexes to createdTapFileName OperatorSpecInfos
        -report reportFile
                Detailed validation report per-error (if missing, goes to STDERR)
        -iv redefinedValidations.xml
                customization of validation process
        -s summaryFile
                Log validation summary in a file
        -rtf rtfFile
                Consise validation report in .RTF output
        -rap createdRapFileName
                RAP file containing errors (generated only when severe or fatal errors exist)
        -rapVer createdRapFileVersion
                RAP file version, e.g. "1.5"
        -rapFSN createdRapFileSequenceNumber
                RAP file sequence number, e.g. "10000"
        -rapPartner createdRapFileRoamingPartner
                Optional RAP file roaming partner, e.g. "DEUD2"
        -rapExtraCalls callFile
                Optional file with call indexes for calls to be included in RAP
        -rapAckIn inputRapFile
                Optional input RAP file (for generation of RAP Acknowledgement file)
        -rapAckOut outputRapAckFile
                Optional output RAP Acknowledgement file
                output version number
                increase verbosity (you can use it more than once, e.g. -vv)
                this help message

Notice that there is only one mandatory input argument, the TAP3 input file. The optional arguments can be used to fine-tune the validation process as follows:

  • By using the RAP related options, you can generate a RAP (1.4 or 1.5) file with the validation errors (severe and fatal). The generated RAP file can be extended with additional calls, read from an external file that specifies calls (based on index: see option "-rapExtraCalls").
  • By using the "-o outputTAP3file" argument, you can request a cleanup of severe calls; all calls causing severe errors will be removed, and AuditControlInfo will be updated to reflect the changes caused by these removals. The original input file remains unharmed; all these changes are performed in the outputTAP3file passed in the argument.
  • All the errors and warnings identified by the validation procedure are sent to the standard error output of the application, unless you use the "-report reportFile.txt" argument to redirect it to a file.
  • Many validations are checking to see if a value is inside a set of allowed values. Perhaps your organization is using a new value not anticipated by the standard, and you want to ignore these reports. Or perhaps, a specific validation depends on bilatteral agreements with a specific PMN, and you want to have different validation rules per PMN. Then again, maybe a specific validation rule is a well known issue with your billing system and you want to ignore it, because you've reached an understanding with the receiving PMN and they don't complain about it.

    You can control all that and more, through a powerful mechanism: a configuration XML file you pass the validator through the "-iv ConfigurationFilename.xml" argument.

  • The validation output is rather verbose: it pinpoints all the details of the specific errors. If you want a less verbose ASCII summary, request one with "-s summaryFile.txt".
  • Perhaps you want the summary to be nicely formatted: instead of "-s", use "-rtf rtfFilename.rtf" and the summary report will be nicely formatted inside an RTF (Rich Text Format) file.
  • You can create RAP Acknowledgment files for incoming RAP files.
The redefined validations XML file enables the user to override default validation rules in a number of ways:
  • Toggle (enable/disable) for a specific validation rule.
  • Change the severity of a rule (e.g. from 'severe' to 'warning' or to 'fatal')
  • Change the set of permissible values for value range checks
  • Change bilaterally agreed parameters (as defined in TD57 standards, where bilateral refers to the two PMNs, the sender and the recipient)
The module returns the maximum amongst the following values:

  • 0 if no fatal or severe errors or warnings were found
  • 1 if at least one warning was found
  • 2 if at least one severe error was found
  • 3 if at least one fatal error was found
You can "glue" this component with a simple script monitoring a directory (perhaps an output directory of your rating engine), and automatically validate all your TAP-out files prior to sending them to a target PMNs. 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