Quintum Technologies CDR - Manual (Page 3)

Quintum Tenor CMS CDR Page 1
Tenor CMS CDR Overview
The Tenor CMS generates a Call Detail Record (CDR) at the completion of each
call. The CDR data string contains call information such as call date and time, call
length, calling party, called party, etc. You can capture billing type data, which can
be used to create billing reports.
The last 9600 CDRs generated are stored by the Tenor CMS in a circular buffer.
This means that any number of CDRs over 9600 will overwrite the existing CDRs
– in other words; first in, first out. We advise that you set up a PC or Workstation to
act as a CDR Server responsible for receiving the CDRs as they are generated.
Up to four (4) servers can be set up to collect CDRs from each CMS. The server is
responsible for capturing CDRs by TCP/IP, processing/storing them in permanent
memory, and producing billing records. If the CMS is reset from the Command Line
Interface (CLI) in Monitor Mode, it will retain all CDR Records in the buffer. If the
Tenor is reset in any other manner (power cycle, etc.), any CDRs not collected from
the CMS will be lost when it is reset.
There is a configuration parameter command, CDRFormat, that is used to choose
which of the three (3) possible Call Data Record output formats (Standard,
Extended, or Extended-CMS – see details below) you want sent to your CDR Server
from the Tenor. You can also specify if you would like the CDR Server and the CMS
to go through a Session ID synchronization process upon connection. This is done
by using a unique Session ID number to confirm that neither unit has been reset or
“power cycled,” and that the CMS has delivered all call records to the CDR Server.
The CDR Server Software and Billing Software mentioned are third-party software,
and are not supported by Quintum.