This is TikiWiki 1.9.7 -Sirius- © 2002–2006 by the Tiki community Thu 20 of Dec, 2007 [16:09 UTC]

User Manual RCDREL

print

Overview


The CDR logger collects signaling event reports from multiple instances of ss7boost. The events are stored in a flat file in the order in which they are received. The information in the flat files can be read into an RDBMS for report generation and long term storage. CDR Logger and the RDBMS should run on a machine that is physically different from any of the the SMG feeding it information so that logging, sorting, and reporting does not impact the real-time performance of the SMG.

Contents


Features


  • Built in configurable periodic file rotation.
  • Collects information from multiple SMG.
  • CSV format output files are compatible with spreadsheets and databases.
  • Configurable location and file name prefix for CDR files.
  • Fine grained epoch-based time-stamps

Installation


Use the SMG installer as follows:
  1. cd /usr/loca/smginstall-<revision>
  2. ./smginstall cdr_logger

Or you can manually do the following:
  1. Copy binary executable file cdr_logger to /usr/local/ss7box/
  2. Copy cdr_logger.conf to /etc/ss7box

Configuration


The contents of the configuration file is as follows:

# This is the cdr_logger.conf file used by cdr_logger.
# Copyright (c) 2006 Xygnada Technology, Inc.

[CONNECT]
# Opposite config should be used by CDR event pushers like ss7boost and
# sangoma_mgd
#
#       Local
#       address                 port
        192.168.1.141           55011
#       Remote (don't care, not used)
#       address                 port
        192.168.1.202           55011

[OUTPUT]
# CDR file path and prefix              file rotate period (minutes)
/usr/local/ss7box/cdr/cdrfile-          30

Operation


Note that ss7boost and CDR Logger may be running on separate machines.

  1. Start the CDR Logging daemon.
    1. cd /usr/local/ss7box
    2. ./cdr_logger
      Use
      ./cdr_logger -h
      for help with command syntax.
  2. Start CDR ouput on ss7boost
  3. Verify functioning
    1. Examine the contents of /var/log/messages on the CDR Logger machine to see the report on opening the CDR file.
    2. Verify calls are being made through SMG. Place some tracer test calls.
    3. List the detailed contents of the subdirectory for CDR files; ensure the CDR file is growing as calls are being made.
    4. Edit the current CDR file to review the contents. Search for evidence of test calls that might have been made.

CDR Log File Format


The CDR log file is a sequence of lines where each line is a set of comma separated values. Each lines corresponds to a call event in ss7boost. There are four line types:
  1. Callstart
  2. IAM
  3. Common
  4. Release

Call Event Field Reference

mt - message type
md - message direction
sy - system id
y - year
mn - month
d - day
h - hour
m - minute
s - second
sn - call serial number
es - epoch timestamp seconds
esu - epoch timestamp micro-seconds
cs - call state
cd - call direction
su - csupid, call setup id
tg - trunk group
sp - span
ch - chan
ci - circuit id code
dc - called number digit count
dd - called number digits
gc - calling number digit count
gd - calling number digits
gpi - calling number presentation indicator
rc - release cause

Call Event Record: Callstart


Message Type: 128

mtmdsysnymndhmisesesucscd
1281102006092910231711594205408501


Call Event Record: IAM


Message Type: 1001

mtmdsysnymndhmisesesucscdsutgspchcidcddgcgdgpi
10010102006092910231711594205414001000141111422220


Call Event Record: Common


Message TypeValue
a130
d131
b1012
c501


mtmdsysnesesucs
13011011594675265900262002
5011101159467531 5930451009
101611011594675321582901009
13101011594675321583981009


Call Event Record: Release


Message Type: 1012

mtmdsysnesesucsrc
10120101159467531593128100916


Creating Call Records


The CDR Logger files are designed to be imported to a spreadsheet or database for storage, sorting, and reporting. A call report is created by first sorting on the system id (sy), then by the epoch time (es/esu), and then by the call serial number (sn). This will group the calls by system, time, and call. The call start time, end time, and duration are derived by using the calendar date/time and epoch times.

Schema Example

The call event records can be parsed in to a dB using a schema as shown in this section.

mtmdsysnymndhmisesesucscdsutgspchcidcddgcgdrc
1281102006092910231711594675205408501---------
10010102006092910231711594675205412400100014111142222
130110------11594675265900262002
1012010------11594675265900642002
501110------1159467531 5930451009
1012010------11594675315931281009
1016110------11594675321582901009
131010------11594675321583981009


Created by: mike last modification: Tuesday 11 of September, 2007 [20:03:05 UTC] by mike


Menu [hide]
Toggle  Wiki
Powered by TikiWiki Powered by PHP Powered by Smarty Powered by ADOdb Made with CSS Powered by RDF
RSS Wiki
[ Execution time: 0.93 secs ]   [ Memory usage: Unknown ]   [ 28 database queries used ]   [ GZIP Disabled ]   [ Server load: 3.79 ]