Showing results for 
Search instead for 
Did you mean: 

Call Logging

Hi There,

One of our clients is looking to be able to tell who calle where and when.

I know we can get theinformation through CDR logs, and I know that we can buy software to do full call accounting but thats way overkill for what they are wanting.

Just want to be able to pull the CDR's in so that they can be searched, and show that extension 356 did or didnt call a number on a specified day. etc.

Any suggestions of anything that can do this????



hi Graeme,

At one site I have the CDRs being imported into a database for similar purposes, and came across some issues you may also find. The biggest one I came across is that the time format in the CDRs doesn't match the date/time datatype of the database, or an easily converted datatype: in the end the imported CDRs have been treated as pure text, then stripped down to it's components, which are then in turned into correct database datatypes. The next biggest problem is something that is totally understandable but mildly frustrating: the same call can appear in multiple CDRs, with different H323-conf-id values (if you watch syslog with a call going through a complicated transfer sequence, with accounting debug on, you'll see it happening), so how do you isolate a single call in all it's steps? (In your example, if extension 356 called extension 366 but the call was then transferred on out to 1-800-number-that-shouldn't-have-been-called-by-356, you won't see that as a call from 356?). You can track on feature correlation id, and select calls based on "h323_conf_id in feature_correlation_id" and you should see all of the call legs.

You'll find you're collecting far more data than you wish if you just import all CDRs exported via ftp: of the 120-or so fields in each record, I think we actually use thirty (at the very most) in this particular application - and I'm including derived fields in that. If you collect CDRs using RADIUS you can filter which fields are reported, but afaik CCA doesn't provide that option? (Please - anyone - if I'm wrong let me know!). CCA does let you export via ftp, and it also lets you setup syslog, but getting plain text via ftp is easier than syslog into database.


Message was edited by: ANDY BILLINGTON. (Added reference to feature correlation id vs h323 conf id)


Hi Graeme,

I admit that a lot of people believe logging CDR's is overkill. However as this is an off-the-shelf solution it can work out a lot cheaper in terms of both cost and time than a self-build solution. Prices from £1250 for up to 100 users but as its pretty much plug-and-play you waste no time with config etc.

You can give them a free demo as proof of concept if you like. That way the solution should prove itself! Alternatively get a free copy for in-house and test before recommending :-S

More information is available here:

@Andy: You can collect RADIUS accounting from a UCME, but not via the CCA.  There are several IOS commands you need to issue to set it up.  We use the RADIUS output for our product, using a RADIUS server built into the system to save setup time.  Cisco have an article about setting up RADIUS accounting available here:

Best regards,