Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
GoogleCodeExporter opened this issue May 13, 2015 · 7 comments
Open

Comments

@GoogleCodeExporter
Copy link

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 [email protected] on 21 Jun 2012 at 8:17

@GoogleCodeExporter
Copy link
Author

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 [email protected] on 25 Jun 2012 at 8:05

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 25 Jun 2012 at 8:05

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

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

Original comment by [email protected] on 25 Jun 2012 at 8:08

@GoogleCodeExporter
Copy link
Author

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 [email protected] on 25 Jun 2012 at 8:37

@GoogleCodeExporter
Copy link
Author

> 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 [email protected] on 26 Jun 2012 at 4:07

@GoogleCodeExporter
Copy link
Author

> 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 [email protected] on 26 Jun 2012 at 4:19

@GoogleCodeExporter
Copy link
Author

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 [email protected] on 8 Oct 2013 at 3:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant