Archive for February, 2010

Let me start by saying the built in CDR displaying for Cisco Unified Communications Manager Express (CUCME from now on) is rubbish…

I’ve just spent 20mins checking the built in CDR display on 6 systems and they all show the following:

I think I’ve been fortunate enough to see this table populated once. I think that’s down to me configuring error logging to an external server and the CDRs are sent there too.  Even if that table is full, you cant do anything with it, other than look at the last 100 or so calls. Good luck trying to do any reports.

The alternative is to view the raw CDRs yourself.

%VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 1, ConnectionId EE1939A9664E5E2D4ADF9103208E0712, SetupTime 21:47:17.643 GMT Fri Feb 5 2010, PeerAddress 123, PeerSubAddress , DisconnectCause 13  , DisconnectText no use
%VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:CFNA,ft:02/05/2010 21:47:32.645,frs:0,fid:9489,fcid:EE1939A9664E5E2D4ADF9103208E0712,legID:1A5A,frson:3,fdcnt:1,fwder:123,fwdee:907971675495,fwdto:299,frm:123,bguid:EE193
%VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:02/05/2010 21:47:17.628,cgn:907971111111,cdn:123,frs:0,fid:9488,fcid:EE1939A9664E5E2D4ADF9103208E0712,legID:1A5B,bguid:EE1939A9664E5E2D4ADF9103208E0712
%VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId EE1939A9664E5E2D4ADF9103208E0712, SetupTime 21:47:17.626 GMT Fri Feb 5 2010, PeerAddress 07971111111, PeerSubAddress , DisconnectCause 10  , DisconnectTex
%VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:CFNA,ft:02/05/2010 21:47:32.645,frs:0,fid:9489,fcid:EE1939A9664E5E2D4ADF9103208E0712,legID:1A5C,frson:3,fdcnt:1,fwder:123,fwdee:907971111111,fwdto:299,frm:123,bguid:EE193
%VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:02/05/2010 21:47:17.620,cgn:07971675495,cdn:01388123456,frs:0,fid:9487,fcid:EE1939A9664E5E2D4ADF9103208E0712,legID:1A5A,bguid:EE1939A9664E5E2D4ADF9103208E0712
%VOIPAAA-5-VOIP_CALL_HISTORY: CallLegType 2, ConnectionId E62B98C811D611DFAF5B9C9D1F42291A, SetupTime 21:47:32.686 GMT Fri Feb 5 2010, PeerAddress 299, PeerSubAddress , DisconnectCause 10  , DisconnectText normal
%VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:CFNA,ft:02/05/2010 21:47:32.645,frs:0,fid:9489,fcid:EE1939A9664E5E2D4ADF9103208E0712,legID:1A5C,frson:3,fdcnt:1,fwder:123,fwdee:907971111111,fwdto:299,frm:123,bguid:EE193
%VOIPAAA-5-VOIP_FEAT_HISTORY: FEAT_VSA=fn:TWC,ft:02/05/2010 21:47:32.669,cgn:907971675495,cdn:299,frs:0,fid:9492,fcid:EE1939A9664E5E2D4ADF9103208E0712,legID:1A5C,bguid:EE1939A9664E5E2D4ADF9103208E0712

Good luck reading that, that’s me calling my desk phone at work, and then the call forwarding to voice mail.

So, I’ve decided I’m going to tackle this issue myself and make my own Call Reporting system, the idea has been spinning around in my head for a while.

This is how I intend it to work, subject to a rethink or brain wave.

1. CUCME sends CDR to external syslog server.
2. Syslog server splits logs into 30minute segments ( I need to find a syslog that will do this)
3. Web APP checks every 45mins for the oldest syslog file, parses this to sql database then archives the log.
4. Web front end to run reports.

Sound simple?

I like making life hard for myself so I’ve decided to develop the web app with Ruby on Rails. The only reason for this is I’ve used PHP a lot, which would no doubt do the job, but I fancied learning something new along the way.

Wish me luck!