CDRs generated by the Perimeta SBC are processed by the TransNexus NexOSS software to create near real time traffic reports, fraud alerts and billing reports. CDR files generated by Perimeta are pushed to an OSPrey server where they receive initial mediation before being collected by NexOSS for processing. The information source for this document is the Perimeta Operations and Maintenance Guide, PMC-005-Issue 3.7.40-Release 1 2 General Perimeta Information
Except the calls rejected for 401 Unauthorized, all calls are reported by Perimeta.
One single CDR per call except transferred calls.
4 CDR types, Basic CDR, Partial CDR, Long duration record and Audit log record, are generated.
Both FTP and SFTP protocols are support to upload billing files to remote billing servers.
Billing file time limit is configurable from 1 minute to 24 hours.
Uploading frequency is configurable from 1 minute to 24 hours.
The solution supports Perimeta XML-format billing files in both original XML format and gzip compressed format. The XSLT feature of Perimeta is not used.
The solution supports Perimeta Basic CDR type.
This is the Perimeta feature that exports CDR files to an external location, such as the OSPrey server.
Remote billing (OSPrey) server information
Protocol, FTP or SFTP
IP address of OSPrey server
Port, 21 for FTP and 22 for SFTP by default d. Target folder on OSPrey server home/ossadmin/OSS/SDReporter/cdrconverter/data/INPUT/Perim eta/index, index is 1 to 32.
If there are multiple Perimeta SBCs, each one must use different target folder with a different index number.
For example:
home/ossadmin/OSS/SDReporter/cdrconverter/data/INPUT/Perimeta/1
and
home/ossadmin/OSS/SDReporter/cdrconverter/data/INPUT/Perimeta/2 2
Perimeta configuration information
Billing file name prefix and suffix. It is not used by the TransNexus solution.
Billing file time limit and uploading frequency. Depending on customer requirements, they are normally configured shorter than 5 minutes.
Billing file time limit must be between 1 minute to 24 hours.
Uploading frequency is configured using uploading interval, which must be a factor of 60. c. Uploading error alert is optional.
You must be super or admin user, and use the Session Controller command line interface (CLI) on a Signaling Session Controller or Integrated Session Controller to turn XML billing feature on.
Select “Admin”.
Select “Billing”.
Select “Modify upload configuration”.
Type the protocol, FTP or SFTP used for the remote billing server, then press Enter.
Type the IP address of the remote billing server, then press Enter.
Type the prot of the remote billing server, then press Enter.
Type the username needed to access the remote billing server, then press Enter.
Type the password needed to access the remote billing server, then press Enter.
Type the target directory on the remote billing server, then press Enter.
Optionally, type the filename prefix and suffix, then press Enter.
Type None for the transform applied before uploading the billing files to the remote billing server, then press Enter.
Type 5, then press Enter.
Type the uploading interval, say 1 minute, then press Enter.
Optionally, configure uploading error alert.
Select “Turn on automatic uploads”.
Type 1, then press Enter.
config
sbc
signaling
billing
method xml
file-flip period timeLimit, say 300s.
end
exit
Select “Admin”.
Select “Billing”.
Select “Upload billing files now”.
Type 1, then press Enter.
CDR files should be uploaded to target directory on the external server.