CDR on Call Manager Express (CME)

[rx8guy]

Does anyone know how to get a CDR connection to a Cisco Call Manager Express? Any input/info is much appreciated.

 

[podwaje]

rx8guy,

The call history record is based on IOS CDR, which you can export to
syslog or radius server.

So if you wants to do it in radius you can open with radius team or syslog
team and they will help you with this.

This is what i got from an internal white paper at cisco. we never went forward with this but it should point you in the right direction. you can also view limited call history through the GUI. the command to change the amount of records is:

dial-control-mib max-size <# of entries>
dial-control-mib retain-timer <time in mins>

The maximum number of calls contained in the table can be set to a number between 0 and 500 using the dial-control-mib command in global configuration mode.



WHITE PAPER:

Cisco IOS Telephony Service allows you to log Call Detail Records (CDRs)
from a Cisco IOS Telephony Service router for accounting or billing
purposes. We recommend that an external authentication, authorization, and
accounting (AAA) server (RADIUS or TACACS) be used to provide CDR logging,
post call record processing, and a billing report generation facility.
Radius server MindCTI can be used to provide billing support and Cisco ACS
server may also be used to view CDR details.

In the case if an AAA server is not available, it is also possible to use
the syslog capabilities of the Cisco IOS Telephony Service router to log
VoIP CDRs to an external syslog server. These records are in comma
separated variable (CSV) format and therefore can easily be loaded and
processed by an external software application such as a spreadsheet, or a
database. The syslog server software can run on a basic PC. Basic syslog
server applications can be downloaded from the Internet. Cisco makes no
recommendations on any particular type or version of syslog server
software. Multiple syslog servers can be specified for redundancy on a
heavy utilized network as Syslog uses UDP as the underlying transport
mechanism and data packets are unsequenced and unacknowledged.

For the timestamp on the CDR to be correct, there is a requirement for the
Cisco IOS Telephony Service router to be configured for time
synchronization via an Network Time Protocol (NTP) time source so that the
start and stop times of each CDR will not be a zero (null) value. If an
external NTP source is not available, the IOS Telephony Service router
needs to be set as a NTP master.

3.3.6.1 Log CDR for accounting and billing purpose to a Syslog Server

Following is a sample configuration that enables the Cisco IOS Telephony
Service router to generate VoIP CDRs and send them to an external syslog
server:

telephony-service#(config) service timestamps log datetime msec localtime
telephony-service #(config) aaa new-model
telephony-service #(config) aaa authentication login default none
telephony-service #(config) aaa accounting connection h323 start-stop
radius
telephony-service #(config) gw-accounting syslog
telephony-service #(config) logging 172.19.153.129
!!! 172.19.153.129 is the ip address of syslog server, multiple servers
may be specified

To synchronize the Cisco IOS Telephony Service to an external NTP server:
telephony-service #(config) ntp server ip address
!!! ip address - IP address of the time server providing the clock
synchronization

If there is no external NTP time source, use the internal clock as the
time source.
telephony-service #(config) ntp master
To ensure that the timestamps are correct, the router clock should be set
to the correct time
telephony-service #clock set 15:15:00 Oct 31 2001




let me know if this helps

POD

 

[rx8guy]

POD,

thank you for taking the time to answer this post in detail -- it is much appreciated!

i'll inform the group how it works out.

rx8guy