Page 1 of 1

which table should i look for inbound call report??

PostPosted: Sun Mar 09, 2014 1:58 pm
by sufian_bd
Hello All,

I am trying to implement a CDR database system for our call center. And i am fetching data from call_log & Closer_log table like this:

select length_in_sec from call_log where (number_dialed='123123123' OR extension='123123123' OR caller_code='123123123') and start_time between '2014-02-28 00:00:00' AND '2014-02-28 23:59:59';

And

select length_in_sec from vicidial_closer_log where uniqueid='1393610592.76671';

But when i compare this data with my provider they don't match and my CDR's are always less. Please help me which table should i look for inbound call report ?

Thanks

Re: which table should i look for inbound call report??

PostPosted: Sun Mar 09, 2014 6:35 pm
by williamconley
1) Welcome to the Party! 8-)

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Check all tables that end in "_log". Especially those that may involve the word "ingroup" or "did"

4) For your future searches for what happens in mysql, you can turn on mysql logging in the OS and capture all queries (after hours ... make one inbound call to see what queries run ... that sort of thing) and you can also mysqldump the entire database with "one record per line" requested ... then make a call and dump it again and DIFF the two. Very handy to find a table used to make a simple record entry and find out if any OTHER changes were also made.

Happy Hunting 8-)