Guest

Cisco PGW 2200 Softswitch

Option to Disable CDR File Generation on the PGW 2200 Softswitch

Document ID: 59620



Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Information to Disable CDR
      Previous Workaround
      Current Solution
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document explains the open issues to disable the call details record (CDR) on the Cisco PGW 2200. Currently, the Cisco PGW 2200 does not have the ability to completely disable CDR files on an active system. As a result, an enhancement Cisco DDTS has been added to Cisco PGW 2200 Software Release 9.6 to disable CDR file generation, in the event that the customer is not using this information.

Prerequisites

Requirements

Readers of this document should have knowledge of these topics:

Components Used

The information in this document is based on the Cisco PGW 2200 Software Releases 9.3, 9.4, and 9.5.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Information to Disable CDR

Previous Workaround

Until now, there was no way to completely disable CDR file generation on the Cisco PGW 2200, even if you set the cdrDmpr.openCDR=false in the XECfgParm.dat file and change the dmprSink.dat file (in the /opt/CiscoMGC/etc directory) to have this setting:

1 "callDetail" bin "cdr" "../var/log" "../var/spool" 1000 0 0

dmprSink.dat Information

Field Name

Default Value

Description

maxRecs

1000

The maximum number of records that a file can contain before the file is flushed or moved to the spool area. If this is set to 0, then the number of records is unlimited.

maxSize

0

The maximum size of the file before it is moved to the spool area. If this is set to 0, then the size of the file is unlimited.

maxTime

15

The maximum time, in minutes, that the file is allowed to remain open before it is flushed or moved to the spool area.

This does not work because, after you issue the /etc/init.d/CiscoMGC stop and start commands, the CDRs are being written again.

However, there was a partial workaround: if you do not configure a call detail block (CDB) in the XECfgParm.dat for the engine.CDRmessageTypes entry, then you will get an empty CDR record, with only a header and footer. Then, you could optionally change the dmprSink.dat file (with the vi UNIX command only) to change the interval of the empty CDR record. At this point, you will have an empty file with only a header and footer.

You also could set the dmprSink.dat maxTime timer to a high value, such as 60 minutes. For example:

1 "callDetail" bin "cdr" "../var/log" "../var/spool" 1000 0 60

Current Solution

To avoid the need for this partial workaround and disable CDR file generation completely, an enhancement DDTS for the Cisco PGW 2200 was created [CSCec81163 ( registered customers only) ] and was introduced into Release 9.6(x), to provide this option.

Note: For the standby Cisco PGW 2200, refer to Cisco bug ID CSCeb66985 ( registered customers only) , which explains how to disable the CDR dump file on a standby box only.

NetPro Discussion Forums - Featured Conversations

Networking Professionals Connection is a forum for networking professionals to share questions, suggestions, and information about networking solutions, products, and technologies. The featured links are some of the most recent conversations available in this technology.
NetPro Discussion Forums - Featured Conversations for Voice
Service Providers: Voice over IP
Voice & Video: Voice over IP
Voice & Video: IP Telephony
Voice & Video: IP Phone Services for End Users
Voice & Video: Unified Communications
Voice & Video: IP Phone Services for Developers
Voice & Video: General

Related Information



Updated: Feb 02, 2006Document ID: 59620