Call History cucm

vikas01234das · ‎04-12-2022

Hallo Team

How to get call history from cucm of a specific number.

I want to export all call history like dialled call received call etc .

I tried to find it under CDR but this format is not a user friendly.

Client wants some different format .So please suggest what we do.

Shalid Kurunnan Chalil · ‎04-13-2022

Hi Vikas,

The Cisco call manager only provides the raw CDR data.. You have to either perform manual formating of the CDR (CSV, excel files) or may have to use any thirdparty reporting tools like (VoipDetective, Veriphy, Imagicle, 2ring etc) to see the report in simple format.

I recently went thrrough a blog from UC collab team about the Python script to provide the basic CDR reports. you can chek it here.

Hope it helps.

Regards,

djl · ‎04-13-2022

Hi Vikas-

Do you have CLI access the the CUCM Publisher?

When I'm looking for that type of data I typically use this SQL query:

run sql car select globalcallid_callid, datetimestamporigination, datetimestampconnect, datetimestampdisconnect, callingpartynumber, origdevicename, originalcalledpartynumber, finalcalledpartynumber, destdevicename, duration from tbl_billing_data where callingpartynumber like "%9525558890" or finalcalledpartynumber like "%9525558890"
globalcallid_callid datetimestamporigination datetimestampconnect datetimestampdisconnect callingpartynumber origdevicename      originalcalledpartynumber finalcalledpartynumber destdevicename  duration 
=================== ======================== ==================== ======================= ================== =================== ========================= ====================== =============== ======== 
12694248            2022-03-25 14:36:26      2022-03-25 14:36:34  2022-03-25 14:36:44     6515553325         CUBE                19525558890               19525558890            SEPAAAAAAAAAAAA 10       
12695118            2022-03-25 14:50:45      2022-03-25 14:50:50  2022-03-25 14:51:01     6515553325         CUBE                19525558890               19525558890            SEPAAAAAAAAAAAA 11       
12697353            2022-03-25 15:25:38      2022-03-25 15:25:40  2022-03-25 15:25:49     6515553325         CUBE                19525558890               19525558890            SEPAAAAAAAAAAAA 9        
12472160            2022-04-01 12:14:49      2022-04-01 12:14:51  2022-04-01 12:15:31     19525558890        CSFABCD             19525558890               19525558890            SEPAAAAAAAAAAAA 40       
12897756            2022-04-01 12:26:42      2022-04-01 12:26:44  2022-04-01 12:26:46     7635556205         CUBE                19525558890               19525558890            SEPAAAAAAAAAAAA 2        
12897768            2022-04-01 12:26:51      2022-04-01 12:26:53  2022-04-01 12:27:10     7635556205         CUBE                19525558890               19525558890            SEPAAAAAAAAAAAA 17       
12897838            2022-04-01 12:28:05      2022-04-01 12:28:07  2022-04-01 12:28:34     7635556205         CUBE                19525558890               19525558890            SEPAAAAAAAAAAAA 27

^ that format is pretty ugly in the forums... looks better in notepad.

All you should need to do is replace '9525558890' with the phone number you're interested in. Note the '%' at the beginning of the number. This statement is saying the number ends with '9525558890'. I.E. this would also match '19525558890' and 'someradomthing9525558890'.

If your results return lines that have duplicate globalcallid_callid that means there were additional call legs; transferred to voicemail, for instance.

You may need to massage the data to whatever your client is looking for.

Your mileage will very as to how far back your can pull records from. I am only able to go back about 3 weeks in my cluster due to call volume.

DJ

Nithin Eluvathingal · ‎04-13-2022

The CDR details from the CUCM is not that user friendly. You need to use third party to have a better view.

Try the below from CLI and see if it helps. 272 is a user extension.

run sql car select call_type,callingpartynumber, originalcalledpartynumber, datetimestamporigination from car:tbl_billing_data where callingpartynumber in ("272")

djl · ‎04-13-2022

Hi Nithin-

That query doesn't account for inbound calls to 272. Also, without the globalcallid_callid it may not give you a full picture if the call was transferred. With that data it would appear to be a unique call, but it may actually just be a separate call leg.

DJ

Nithin Eluvathingal · ‎04-13-2022

Its just a simple query..