Concurrent Calls report works for 1 day but not for a month

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Select only Concurrent Calls
2. Select 1 month or more for Call dates
3. Run the report and it takes for ever and won't come back with report.

What is the expected output? What do you see instead?
It should show concurrent calls for whole month with MAX Calls showing

What version of the product are you using? On what operating system?
Latest 0.9x

Please provide any additional information below.

Original issue reported on code.google.com by bruce....@sharpcall.ca on 21 Jun 2012 at 8:17

[GoogleCodeExporter]

This is a very `heavy` report, so it is better not to run it on large time 
intervals. I'm going to optimize it in the near future.

Original comment by igor.oku...@gmail.com on 25 Jun 2012 at 8:05

[GoogleCodeExporter]

Original comment by igor.oku...@gmail.com on 25 Jun 2012 at 8:05

• Changed state: Started

[GoogleCodeExporter]

One can move the reports to another idle server and run the report so being 
heavy might not be an issue.

Original comment by bruce....@sharpcall.ca on 25 Jun 2012 at 8:08

[GoogleCodeExporter]

Also currently reports of max call peaks doesn't differentiate between inbound, 
outbound, or internal (ext-to-ext) calls.

Reports must show and differentiate Inbound peak calls, and outbound peak calls 
in separate reports. Also, provide internal peak calls as a third separate 
report.

This feature will make the program very useful.

Original comment by bruce....@sharpcall.ca on 25 Jun 2012 at 8:37

[GoogleCodeExporter]

> Also currently reports of max call peaks doesn't differentiate between 
inbound, outbound, or internal (ext-to-ext) calls.

The system does not know anything about what kind of calls to internal and what 
external. Just run this report 4 times with different filters and get the 
required results ( all / inbound / outbound / internal ).

Original comment by igor.oku...@gmail.com on 26 Jun 2012 at 4:07

[GoogleCodeExporter]

> One can move the reports to another idle server and run the report so being 
heavy might not be an issue.

If you need to run it right now, just increase max_execution_time in 
/etc/php.ini.

Original comment by igor.oku...@gmail.com on 26 Jun 2012 at 4:19

[GoogleCodeExporter]

Have there been any updates on this matter?   Its been over a year and I am 
having issues with the concurrent call report.  It appears to run forever and 
display nothing once completed.

Original comment by bfer...@gmail.com on 8 Oct 2013 at 3:22