Cisco Call Manager v6/v7, UC560 and router CDR formats

Advanced PBX Data Logger includes 4 parsers for Cisco systems. This page gathers them in one place. For each system you will find how the call records reach the logger, the parser to select, and the 249 fields in total that these parsers extract for PBX Reports or a database. Of these, 2 over FTP; the rest are identified by their record layout and can arrive over a serial port or a LAN connection. The settings apply to our logger; other call accounting software may expect a different configuration.

Systems on this page

• Cisco Call Manager (CSV) v6 · FTP, 86 fields
• Cisco Call Manager (CSV) v7 · FTP, 102 fields
• Cisco Router CDR · Serial or TCP, 24 fields
• Cisco UC560 · Serial or TCP, 37 fields

Connecting the logger

Add a data source in PBX Data Logger that matches the interface named in each section: RS232 for a serial SMDR port, TCP client when the PBX accepts connections, TCP server when the PBX pushes records to the logger, or FTP for systems that write CDR files. Then open Modules → Query Parse Filter → Data query, click Setup and select the parser named in the section. The general steps are shown on the SMDR listener page; every other supported system is listed on the supported PBX index.

Cisco Call Manager (CSV) v6

Parser: Cisco Call Manager (CSV) v6
Connection: CDR files downloaded by FTP from the PBX or its server and parsed on arrival.
Fields extracted: 86

Cisco Unified Communications Manager

CDR Repository Manager

Within a Cisco Unified Communications Manager server or cluster, one instance of the CDR Repository Manager runs on the CDR Repository server or node. It manages CDR files that are received from the Cisco Unified Communications Manager nodes and periodically sends the files to the specified customer/third-party billing servers via FTP/SFTP. Our PBX Data Logger polls the FTP server and retrives new data. You should add the "File" data source type and configure a FTP or SFTP connection with the FTP server.

When the file arrives on the CDR Repository server or node, the CDR Repository Manager detects it. The system archives the file in a directory that is dedicated to the date that is indicated by the UTC timestamp that was placed in the file name when the file was created.

If any external billing server is specified in the CDRM configuration, the system creates an empty file in each of the corresponding folders for CAR and the billing servers, if CAR or the corresponding billing server is activated. The CDR Agent monitors new CDR/CMR files that are generated on CallManager servers or nodes by the call processing component. It sends the files to the CDR Repository node and then deletes the local copy after the file is pushed out. The file sender component of the CDR Repository Manager detects these empty files and sends the file to the destination with the specified method. If the delivery is successful, the system removes the empty file in the destination directory. Every Cisco Unified Communications Manager can generate one CDR file and one CMR file every minute for up to 1 hour. You can configure the maximum disk space that is used for storage of CDR files in the CDR Repository through provisioning. The File Manager component of the CDR Repository Manager runs hourly. When the File Manager runs, it deletes files with dates outside the configured preservation duration. It also checks whether disk usage has exceeded the high water mark. If so, the system deletes the processed CDR files until the low water mark is reached, starting with the oldest files. However, if any CDR file to be deleted was not successfully sent to the specified billing server, the system leaves it in the CDR Repository and raises a notification or alarm. The system creates a flag file during the configured maintenance window, which denies access to the CDR files for the CDR onDemand Service. The system removes the flag file after the maintenance window expires.

For detailed procedures on configuring the CDR Repository Manager and customer billing servers, see "Cisco Unified Communications Manager Call Detail Records Administration Guide"

Architecture

CDR fields

For detailed description of CDR fields, see here:
Cisco CallManager 6
Cisco CallManager 7
Cisco CallManager 8

Settings from the manufacturer's documentation

Taken from Veramark - Connectivity Guide. Values are those stated in the documentation; confirm them against your firmware release.

Switching SMDR output on, as documented

1. Access Service > Service Parameters > [CCM server] Services > Cisco CallManager and set the parameter CdrEnabled = True.

Data items: Cisco Call Manager (CSV) v6

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

1,1,403xxxx,266xxxxx,130xxxxxxx,1,0,411xxxxxx,"5818","",0,16,4,411xxxxxx,21488,6,20,0,0,0,0,0,0,"0","0",266xxxxx,1,0,562xxxxxx,"5661","5661","",0,0,4,562xxxxxx,16558,6,20,0,0,0,0,0,0,"0","0",130xxxxxxx,130xxxxxxx,"5661","bb100ead-70f3-4351-84e6-7414f388xxxx","","","","",41,"SEP006440B4EA46","SEP002xxxxxxBA5",12,0,0,0,0,0,0,"StandAloneCluster",0,"","",0,"",3,3,0,0,64,64,""
1,1,403xxxx,266xxxxx,130xxxxxxx,1,0,596xxxxxx,"5674","",0,16,4,596xxxxxx,17260,4,20,0,0,0,0,0,0,"0","0",266xxxxx,1,266xxxxx,-132xxxxxxx,"#989xxxxxxxxx","#989xxxxxxxxx","",0,0,4,0,0,2,20,0,0,0,0,0,0,"0","0",0,130xxxxxxx,"#989xxxxxxxxx","c9cf9d28-832f-4dee-9f74-f9c8d3b36f86","Mobile Prt","","Mobile Prt","Mobile Prt",0,"SEP002xxxxA04EA","gate002.televersal.ru",12,0,0,0,0,0,0,"StandAloneCluster",0,"","",0,"",3,1,0,0,64,64,""
1,1,403xxxx,266xxxxx,130xxxxxxx,1,0,118xxxxxx,"5234","",0,0,4,0,0,0,0,0,0,0,0,0,0,"0","0",266xxxxx,0,0,0,"","","",0,0,4,0,0,0,0,0,0,0,0,0,0,"0","0",0,130xxxxxxx,"","17e16361-70be-40bd-9709-536xxxxbc222","","","","",0,"SEP002xxxxC4AF4","",16,0,0,0,0,0,0,"StandAloneCluster",0,"","",0,"",3,0,0,0,0,0,""

Cisco Call Manager (CSV) v7

Parser: Cisco Call Manager (CSV) v7
Connection: CDR files downloaded by FTP from the PBX or its server and parsed on arrival.
Fields extracted: 102

Cisco Unified Communications Manager

CDR Repository Manager

Within a Cisco Unified Communications Manager server or cluster, one instance of the CDR Repository Manager runs on the CDR Repository server or node. It manages CDR files that are received from the Cisco Unified Communications Manager nodes and periodically sends the files to the specified customer/third-party billing servers via FTP/SFTP. Our PBX Data Logger polls the FTP server and retrives new data. You should add the "File" data source type and configure a FTP or SFTP connection with the FTP server.

When the file arrives on the CDR Repository server or node, the CDR Repository Manager detects it. The system archives the file in a directory that is dedicated to the date that is indicated by the UTC timestamp that was placed in the file name when the file was created.

If any external billing server is specified in the CDRM configuration, the system creates an empty file in each of the corresponding folders for CAR and the billing servers, if CAR or the corresponding billing server is activated. The CDR Agent monitors new CDR/CMR files that are generated on CallManager servers or nodes by the call processing component. It sends the files to the CDR Repository node and then deletes the local copy after the file is pushed out. The file sender component of the CDR Repository Manager detects these empty files and sends the file to the destination with the specified method. If the delivery is successful, the system removes the empty file in the destination directory. Every Cisco Unified Communications Manager can generate one CDR file and one CMR file every minute for up to 1 hour. You can configure the maximum disk space that is used for storage of CDR files in the CDR Repository through provisioning. The File Manager component of the CDR Repository Manager runs hourly. When the File Manager runs, it deletes files with dates outside the configured preservation duration. It also checks whether disk usage has exceeded the high water mark. If so, the system deletes the processed CDR files until the low water mark is reached, starting with the oldest files. However, if any CDR file to be deleted was not successfully sent to the specified billing server, the system leaves it in the CDR Repository and raises a notification or alarm. The system creates a flag file during the configured maintenance window, which denies access to the CDR files for the CDR onDemand Service. The system removes the flag file after the maintenance window expires.

For detailed procedures on configuring the CDR Repository Manager and customer billing servers, see "Cisco Unified Communications Manager Call Detail Records Administration Guide"

Architecture

CDR fields

For detailed description of CDR fields, see here:
Cisco CallManager 6
Cisco CallManager 7
Cisco CallManager 8

Data items: Cisco Call Manager (CSV) v7

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

1,1,111xxxx,287xxxxx,132xxxxxxx,1,0,121xxxxxxx,"5348","",0,0,4,0,0,0,0,0,0,0,0,0,0,"0","0",287xxxxx,1,287xxxxx,-132xxxxxxx,"#989xxxxxxxxx","#989xxxxxxxxx","",0,38,4,0,0,0,0,0,0,0,0,0,0,"0","0",0,132xxxxxxx,"#989xxxxxxxxx","15d8af83-165b-459e-8e5f-42a84c043b76","Mobile Prt","","Mobile Prt","Mobile Prt",0,"SEP002xxxxCBAD7","10.0.1.177",0,12,0,0,0,0,0,"StandAloneCluster",0,"","",0,"",3,1,0,0,0,0,"","","","10.9.145.72","",0,0,0,0,0,0,0,0,0,0,0,0
1,1,111xxxx,287xxxxx,132xxxxxxx,1,0,-1785722614,"5363","",0,0,4,0,0,0,0,0,0,0,0,0,0,"0","0",287xxxxx,1,287xxxxx,-132xxxxxxx,"#983xxxxxxxxx","#983xxxxxxxxx","",0,38,4,0,0,0,0,0,0,0,0,0,0,"0","0",0,132xxxxxxx,"#983xxxxxxxxx","e59d6119-c83a-42e2-bcf0-5d4a24934c11","Mej_Gorod Prt","","Mej_Gorod Prt","Mej_Gorod Prt",0,"SEP002xxxxAF7F1","10.0.1.177",0,12,0,0,0,0,0,"StandAloneCluster",0,"","",0,"",3,1,0,0,0,0,"","","","10.9.144.149","",0,0,0,0,0,0,0,0,0,0,0,0
1,1,111xxxx,287xxxxx,132xxxxxxx,1,0,131xxxxxxx,"5376","",0,0,4,0,0,0,0,0,0,0,0,0,0,"0","0",287xxxxx,1,287xxxxx,-132xxxxxxx,"#989xxxxxxxxx","#989xxxxxxxxx","",0,38,4,0,0,0,0,0,0,0,0,0,0,"0","0",0,132xxxxxxx,"#989xxxxxxxxx","f115f9dc-1816-4e4b-ad66-772be212xxxx","Mobile Prt","","Mobile Prt","Mobile Prt",0,"SEP002xxxxA664E","10.0.1.177",0,12,0,0,0,0,0,"StandAloneCluster",0,"","",0,"",3,1,0,0,0,0,"","","","10.9.145.78","",0,0,0,0,0,0,0,0,0,0,0,0

Cisco Router CDR

Parser: Cisco Router CDR
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 24

Data items: Cisco Router CDR

Sample record

As delivered by the system; phone numbers, names and public addresses are masked.

    ReceivePackets 1510, ReceiveBytes 138920
Jun 18 11:15:02.983: %NAME   -5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId BA55719E
    F8C10015 0 1B1E08, SetupTime 11:14:41.683 UTC Mon

Cisco UC560

Parser: Cisco UC560
Connection: Serial printer port or LAN, whichever the system uses for SMDR output. The record layout identifies the format.
Fields extracted: 37

Data items: Cisco UC560

Reports and a database

Once records arrive, the logger writes them to a text file or to any ODBC database in real time, or hands them to the PBX Reports utility for manual, scheduled and e-mailed reports with a built-in web server. See exporting call log data to a database for the database setup.

Related Cisco systems with their own setup pages

Note: Products and companies mentioned here are used only for definition and identification purposes and can be trademarks and/or registered trademarks of the respective companies.