Quintum Technologies CDR User Manual

CDR Implementation Guide

for Quintum Tenors and Tenor CMS

Quintum
Technical
Support
Group

[e-mail]

1-877-435-7553 (toll free-US)
1-732-460-9399

Table of Contents

Tenor CMS CDR Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Establishing a Connection between Tenor CMS and the CDR Server . . . . . . . . 2

Configure CDR Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Configure CDR Server Connection Information on Tenor CMS . . . . . . . . . . . . . . . . . . . . . . .4

Establish Connection between CDR Server and Tenor CMS . . . . . . . . . . . . . . . . . . . . . . . . .4

CDR Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

CDR Field Definitions: Standard Format Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

CDR Field Definitions: Extended Format Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

CDR Field Definitions: Extended-CMS Format Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Settings 3 & 103 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Settings 4 & 104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Disconnect Cause Code List (Field G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

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.

Quintum Tenor CMS CDR Page 1

Establishing a Connection between Tenor CMS and the CDR Server

In order to capture CDRs, a connection between CMS and the CDR server must be
established. Based on configuration, the CMS can either establish a TCP/IP session
with one or both of these CDR servers, or the CDR server can establish a connection
with the CMS. If the latter is the case, where the CDR Server is initiating the
connection, then the CDRServerIPAddr in the CMS should be set to 0.0.0.0.

The following flow diagram illustrates the general transfer of information using
both connection types. More detail is provided in the sections that follow.

Figure 1 CDR Connection Flow

Configure CDR Format

Before attempting to collect CDRs, you should configure the following information.
Through CLI commands under the Prompt Level config-CDRServer-x# (“x” = 1, 2,
3 or 4), you can determine the appropriate output format, and assign CDR Server IP
Address(es), CDR Server Port Number(s), and CDR Server Password information.
Use the following CLI commands: CDRFormat, CDRServerIPAddr,
CDRServerPort and CDRPassWord.

Quintum Tenor CMS CDR Page 2

Table 1: CDR CLI Commands

Command Description

CDRFormat This configuration parameter command is used to choose which of the four (4)

possible Call Data Records output formats you would like sent to your CDR

Server, each with or witho ut Sessio n ID functionality (see below).
CDRServerIPAddr IP address of the CDR server (used to establish connection with CDR server).
CDRServerPort The Application Port number(s) used by the CDR server(s). (Used when the

CMS establishes connection with CDR server.) (Valid values are 9002, 9003,

9004, and 9005)
CDRPassWord Password to be used by the CDR server(s) to gain permission to access the

CMS.

Syntax for the CDRFormat command is as follows:

config-CDRServer-1# set cdrformat {x}

or

config-CDRServer-2# set cdrformat {x}

Table 2: CDRFormat Parameter Settings

Setting Description

0 Gives the Standard CDR output (See next page for output details)
1 Gives the Extended CDR output. (See next page for output details)
3 Gives Extended-CMS CDR output. (See next page for output details)

4 Gives Extended-CMS+ CDR output. (See next page for output details)
100 Same data stream as Selection 0, but adds the Session ID functionality.
101 Same data stream as Selection 1, but adds the Session ID functionality.
103 Same data stream as Selection 3, but adds the Session ID functionality.
104 Same data stream as Selection 4, but adds the Session ID functionality
199 Same data stream as Selection 104, but adds the trunk id parameters (if

configured) and the disconnect leg

Quintum Tenor CMS CDR Page 3