Configuring the Cisco MC3810 to Compile Call Detail Records

The purpose of the Call Detail Records (CDR) feature is to provide tracking records for the calls being processed by the Cisco MC3810. The CDR data is collected by the Cisco MC3810 for all Plain Old Telephone Services (POTS) call attempts and the data is collected for each call leg and also by each Cisco MC3810 involved in the call session. (Call leg refers to one of the following: a) POTS lines if the call both originates and terminates on the same Cisco MC3810; b) POTS line and trunk for calls that either originate and terminate on another Cisco MC3810; or c) two trunks in the case of a tandem call.)

The CDR data is stored in an internal buffer on the Cisco MC3810 at call termination time and becomes available to be polled periodically by the Cisco NMS via the SNMP Get/GetNext function. The CDR call history entries will not be able to retrieve after the Cisco MC3810 power loss or a software reload. The Cisco NMS is the final destination for storing or tailoring the CDR call history table into a suitable report format.

Note The CDR functionality is enabled by default. If you do not plan to use the CDR functionality to compile call detail records, it is recommended that you disable CDR by entering the configuration command dial-control-mib max-size 0.

Configuring Call Detail Records Support

To configure the Cisco MC3810 to compile CDR events, perform the following tasks beginning in global configuration mode:

Step Command Purpose

1

router(config)# dial-control-mib {max-size number | retain-timer number}
Configure the Cisco MC3810 to compile CDR events.

The max-size value specifies the maximum size of the CDR event table. The valid range is from 0-1200, and the default is 50. The value 0 disables the CDR feature, meaning no call history is compiled.

The retain-timer value specifies the length of time in minutes that entries will remain in the call history table. The valid range is from 0-2147483647 minutes, and the default is 15. Setting the value to 0 prevents any call history from being retained.
Note It is recommended that both values be set high enough for the NMS to successfully poll the CDR events, and to access the events in the call history table.

2

router(config)# exit
Exit configuration mode.

3

router# show call history voice record
As an alternative to viewing CDR events via the NMS, display portions of the call history table showing the CDR events. The display only shows a snapshot of the events currently stored in the call history table buffer.

Some call history records may show an empty string for the calling number. This may be caused by certain configurations, but does not necessarily indicate a problem with the call.

Step	Command	Purpose
1	`router(config)# dial-control-mib {max-size number \| retain-timer number}`	Configure the Cisco MC3810 to compile CDR events. The max-size value specifies the maximum size of the CDR event table. The valid range is from 0-1200, and the default is 50. The value 0 disables the CDR feature, meaning no call history is compiled. The retain-timer value specifies the length of time in minutes that entries will remain in the call history table. The valid range is from 0-2147483647 minutes, and the default is 15. Setting the value to 0 prevents any call history from being retained. Note It is recommended that both values be set high enough for the NMS to successfully poll the CDR events, and to access the events in the call history table.
2	`router(config)# exit`	Exit configuration mode.
3	`router# show call history voice record`	As an alternative to viewing CDR events via the NMS, display portions of the call history table showing the CDR events. The display only shows a snapshot of the events currently stored in the call history table buffer. Some call history records may show an empty string for the calling number. This may be caused by certain configurations, but does not necessarily indicate a problem with the call.

Note The CDR event output is not meaningful until after dial peers for Voice over Frame Relay, Voice over ATM, or Voice over HDLC are configured.

The following is a sample of the output obtained using the show call history voice record command showing a local call between two telephones attached to the same Cisco MC3810:

show call history voice record
ConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]
Media=TELE, TxDuration= 1418 ms
CallingNumber=2001
SetupTime=1157801 x 10ms
ConnectTime=1158046 x 10ms
DisconectTime=1158188 x 10ms
DisconnectText=local onhook
 
ConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]
Media=TELE, TxDuration= 1422 ms
CalledNumber=2002
SetupTime=1157802 x 10ms
ConnectTime=1158046 x 10ms
DisconectTime=1158188 x 10ms
DisconnectText=remote onhook

Figure 12-1 shows an example of a tandem call with three Cisco MC3810 concentrators handling the call.

Figure 12-1: Tandem Call Configuration Example for CDR Display

On the first Cisco MC3810 (on the left), where the call originates, the show call history voice record output is the following:

ConnectionId=[0x5BB38AB2 0x3C2D0004 0x0 0x1BD45D]
Media=TELE, TxDuration= 1222 ms
CallingNumber=1001
SetupTime=182383 x 10ms
ConnectTime=182634 x 10ms
DisconectTime=182756 x 10ms
DisconnectText=local onhook
 
ConnectionId=[0x5BB38AB2 0x3C2D0004 0x0 0x1BD45D]
Media=ATM, LowerIfName=ATM0, VPI=0, VCI=1
CalledNumber=2001
SetupTime=182383 x 10ms
ConnectTime=182634 x 10ms
DisconectTime=182756 x 10ms
DisconnectText=local onhook

On the second Cisco MC3810 (in the center) acting as the tandem switch, the show call history voice record output is the following:

ConnectionId=[0x5BB38AB2 0x3C2D0004 0x0 0x1BD45D]
Media=ATM, LowerIfName=ATM0, VPI=0, VCI=1
CallingNumber=1001
SetupTime=8004 x 10ms
ConnectTime=8253 x 10ms
DisconectTime=8376 x 10ms
DisconnectText=remote onhook
 
ConnectionId=[0x5BB38AB2 0x3C2D0004 0x0 0x1BD45D]
Media=FR, LowerIfName=Serial1, DLCI=131
CalledNumber=2001
SetupTime=8004 x 10ms
ConnectTime=8251 x 10ms
DisconectTime=8376 x 10ms
DisconnectText=remote onhook

On the third Cisco MC3810 (on the right) where the call is terminated, the show call history voice record output is the following:

ConnectionId=[0x5BB38AB2 0x3C2D0004 0x0 0x1BD45D]
Media=FR, LowerIfName=Serial1, DLCI=131
CallingNumber=1001
SetupTime=1663593 (10ms)
ConnectTime=1663839 (10ms)
DisconectTime=1663964 (10ms)
DisconnectText=remote onhook
 
ConnectionId=[0x5BB38AB2 0x3C2D0004 0x0 0x1BD45D]
Media=TELE, TxDuration= 1258 (ms)
CalledNumber=2001
SetupTime=1663594 (10ms)
ConnectTime=1663838 (10ms)
DisconectTime=1663964 (10ms)
DisconnectText=remote onhook

Table of Contents