Technical information

Cisco Unified CallManager 4.2(3) Call Detail Record Definition

OL-10659-01

Cisco Unified CallManager CDR Overview

The Cisco Unified CallManager comprises several Windows 2000 Servers that are using Microsoft SQL

clustering method to share common data. Each cluster comprises a publisher and several subscriber

databases.

Microsoft SQL Server 2000 Service Pack 3A, which replaces Microsoft SQL 7.0, gets configured with

only TCP for communications and NT authentication. Named Pipes communications and Mixed mode

authentication no longer get configured.

Note Windows NT Authentication is recommended, although the system supports SQL Authentication.

Setting Cisco Unified CallManager for mixed mode authentication in Release 4.0 and later is

unsupported. Upgrades will fail and the system will have to be changed back to Windows authentication.

The connection logic in the database layer uses Windows NT authentication. All database layer

connections, which are DSN based, use an Open Database Connectivity (ODBC) system DSN,

CiscoCallManager. For more information, see the “Reading Records” section.

Any third party application that connects to the database can change the way that it connects. Beyond

that, everything else remains the same. Both previous and current connections work.

The configuration ensures that web applications that do not require an NT login and use the database

layer, such as CCMUser, run as a different NT user with limited privileges, not ANONYMOUS.

Cisco Unified CallManager generates two different types of call information records: call detail records

(CDRs) and Call Management Records (CMRs). The CDRs store information about the endpoints of the

call and other call control/routing aspects. The CMRs contain information about the quality of the

streamed audio of the call. More than one CMR can exist per CDR.

The CDR records relate to the CMR records via the two globalCallID columns:

• globalCallID_callManagerId

• globalCallID_callId

The database server (publisher) maintains the central copy of the CDR database. When a call is generated

on a subscriber, the Cisco Unified CallManager writes CDRs and CMRs in flat files (text) on the

subscriber databases. The localCDRPath enterprise parameter specifies the directory to which the files

are written. CDR and CMR records periodically pass from each of the subscribers to the publisher, and

the Cisco CDR Insert service reads the records from the flat files and inserts the records into the

centralized SQL database.

The configurable directory that contains the files defaults to \Program Files\Cisco\CallDetail.

Cisco Unified CallManager does not perform any post processing on the records. For more information,

see the “Writing Records” section.

Note Each server (publisher and subscriber) can operate as a call-control engine, but Cisco

recommends that you reserve the publisher server for management processes.