MiCC Database SMDR Data Queries

[mauka]

I have been asked to pull SMDR data proving whether or not a specific user called specific external numbers on specific days.

I have been struggling with the Data Inspectors tool and went searching for the SMDR data in the MiCC databases. It appears that that data is stored in vw_LC_ReportData view and the tblData_LC_Trace table in the CCMStatisticalData database.

I believe that I have written accurate SQL queries but wanted confirmation that I am looking in the correct place and would also like some documentation on the tables and columns. My reseller support has been unable to coordinate time between me, him, and Mitel support.

Does anyone have experience or documentation on these tables?

[sarond]

I normally do this differently and look at the raw SMDR data. Text files (zip after certain age) are stored in the Node directory of the PABX, usually Node_1.

So if you look in C:\Program Files (x86)\Mitel\MiContact Center\DataDirectory\Node_01 there will be files starting with "s" followed by date, this is the SMDR file for that date. e.g. s20250221.txt

You might be able to start with that.

[fishhead64]

Is there a single repository for CDR data? We have a hybrid cloud solution across the Reston and Dallas data centers, plus two backups onsite, multiple EX controllers, 20 AX controllers and have struggled with our Call Accounting provider to filter out duplicate call records.

If we wanted to query all the call records across all these devices, is there one single database for it?

[mauka]

I normally do this differently and look at the raw SMDR data. Text files (zip after certain age) are stored in the Node directory of the PABX, usually Node_1.

So if you look in C:\Program Files (x86)\Mitel\MiContact Center\DataDirectory\Node_01 there will be files starting with "s" followed by date, this is the SMDR file for that date. e.g. s20250221.txt

You might be able to start with that.

I see the raw SMDR files on the MiCC server and it looks like the table in the database has the same data - and possibly even more detail. The SQL query is faster to execute in this case when are unsure about the date range but for the life of my I can't find anything out there that explicitly confirms what the tblData_LC_Trace table is for.