Downloads |
Table Of Contents
show call history voice record
Call Detail Records (CDR)
Feature Summary
Using the Call Detail Records (CDR) functionality, you configure the Cisco MC3810 to compile records of successful calls and failed call events for billing and administrative purposes. You can use a Cisco network management system (NMS) to poll the Cisco MC3810 for CDR events, or display the call records directly on the Cisco MC3810.
Benefits
This feature provides the following benefits:
•
By compiling Call Detail Records, you can keep track of successful and failed call events for billing and administrative purposes.
List of Terms
CDR—Call Detail Record. (Cisco Systems Term)
VNS record of voice or data SVCs, which includes calling and called numbers, local and remote node names, data and timestamp, elapsed time, and Call Failure Class fields.SVC—Switched Virtual Circuit
Virtual circuit that is dynamically established on demand and is torn down when transmission is complete. SVCs are used in siturations where data transmission is sporadic. Called a switched virtual connection in ATM terminology. Compare with PVC.VNS—Virtual Networking Services. (Cisco Systems Term)
Software on some Catalyst 5000 switches that enables multiple workgroups to be defined across switches and offers traffic segmentation and access control.Platforms
This feature is supported on the Cisco MC3810 only.
Prerequisites
The following configuration tasks should be completed before configuring this feature:
•
•
Supported MIBs and RFCs
None.
Configuration Tasks
To configure the Cisco MC3810 to compile CDR events, perform the following tasks beginning in global configuration mode:
Note
Configuration Example
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 recordConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]Media=TELE, TxDuration= 1418 msCallingNumber=2001SetupTime=1157801 x 10msConnectTime=1158046 x 10msDisconectTime=1158188 x 10msDisconnectText=local onhookConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]Media=TELE, TxDuration= 1422 msCalledNumber=2002SetupTime=1157802 x 10msConnectTime=1158046 x 10msDisconectTime=1158188 x 10msDisconnectText=remote onhookshows an example of a tandem call with three Cisco MC3810 concentrators handling the call.
Figure 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 msCallingNumber=1001SetupTime=182383 x 10msConnectTime=182634 x 10msDisconectTime=182756 x 10msDisconnectText=local onhookConnectionId=[0x5BB38AB2 0x3C2D0004 0x0 0x1BD45D]Media=ATM, LowerIfName=ATM0, VPI=0, VCI=1CalledNumber=2001SetupTime=182383 x 10msConnectTime=182634 x 10msDisconectTime=182756 x 10msDisconnectText=local onhookOn 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=1CallingNumber=1001SetupTime=8004 x 10msConnectTime=8253 x 10msDisconectTime=8376 x 10msDisconnectText=remote onhookConnectionId=[0x5BB38AB2 0x3C2D0004 0x0 0x1BD45D]Media=FR, LowerIfName=Serial1, DLCI=131CalledNumber=2001SetupTime=8004 x 10msConnectTime=8251 x 10msDisconectTime=8376 x 10msDisconnectText=remote onhookOn 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=131CallingNumber=1001SetupTime=1663593 (10ms)ConnectTime=1663839 (10ms)DisconectTime=1663964 (10ms)DisconnectText=remote onhookConnectionId=[0x5BB38AB2 0x3C2D0004 0x0 0x1BD45D]Media=TELE, TxDuration= 1258 (ms)CalledNumber=2001SetupTime=1663594 (10ms)ConnectTime=1663838 (10ms)DisconectTime=1663964 (10ms)DisconnectText=remote onhookCommand Reference
The following new or revised commands are used to configure the CDR feature:
•
dial-control-mib
To specify attributes for the call history table, use the dial-control-mib global configuration command.
dial-control-mib {max-size number | retain-timer number}
Syntax Description
Default
The default call history table length is 50 table entries. The default retain timer is 15 minutes.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.3(1)T.
This command first applied to the CDR feature on the Cisco MC3810 in Cisco IOS Release 12.0(1) XA.
Example
The following example configures the call history table to hold 400 entries, with each entry remaining in the table for 10 minutes:
configure terminaldial-control-mib max-size 400dial-control-mib retain-timer 10show call history voice record
To display Call Detail Record (CDR) events in the call history table, use the show call history voice records privileged EXEC command.
show call history voice record
Command Mode
Privileged EXEC.
Usage Guidelines
This command first appeared in Cisco IOS Release 12.0(2)T.
Example
The following example displays a sample of voice call history records showing a local call between two telephones attached to the same Cisco MC3810:
show call history voice recordConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]Media=TELE, TxDuration= 1418 msCallingNumber=2001SetupTime=1157801 x 10msConnectTime=1158046 x 10msDisconectTime=1158188 x 10msDisconnectText=local onhookConnectionId=[0x2C7AEFDC 0x59830001 0x0 0xB0AAA3]Media=TELE, TxDuration= 1422 msCalledNumber=2002SetupTime=1157802 x 10msConnectTime=1158046 x 10msDisconectTime=1158188 x 10msDisconnectText=remote onhookexplains the fields in the sample output.
