Browser error when trying to clear call logs

[c.holloway]

When I try to clear out call logs for a client the browser just hangs and throws an error (below). I have tried various ranges in the custom template but all have the same result. I have also tried various browsers and they all act the same, even after clearing the cache as suggested. Is there any other way to clear the call logs without purging the entire record?

 

[ChrisC_3CX]

Just so that we first get a better understanding of your current setup, please let us know of the following:

• Is this a hosted or on premise machine?
• Is it a VM, what hypervisor is it running on?
• What is the exact OS it is running on?
• What version of 3CX is it? Check in "Dashboard >> Information >> License".
• How many extensions are configured on this instance?
• What are the specifications of this machine?
• If you go to Dashboard, what number of calls can you see under PBX Status >> Call history?

 

[c.holloway]

Just so that we first get a better understanding of your current setup, please let us know of the following:

• Is this a hosted or on premise machine?
• Is it a VM, what hypervisor is it running on?
• What is the exact OS it is running on?
• What version of 3CX is it? Check in "Dashboard >> Information >> License".
• How many extensions are configured on this instance?
• What are the specifications of this machine?
• If you go to Dashboard, what number of calls can you see under PBX Status >> Call history?

It's an on prem Debian, latest stable build, 16.0.9. It's a VM on VMWare 6.5 and there are 500-600 extensions. The VM has 6 cores and 8 GB of ram. The dashboard is reporting over 8 million calls which is why i'm trying to prune this but they don't want to lose all of their recent call history so I have been trying to remove the calls prior to April of this year.

 

[ChrisC_3CX]

First off, I would recommend taking a look at our Hardware Requirements and make sure the 3CX Instance in question is compliant.

In the meantime, try and remove the call logs for a very short period, maybe start by trying a single day, say the 31st of March, does that work or do you get the same error?

 

[c.holloway]

If I'm reading that correctly it does appear we've met the requirements as we would seem to fall in the large range. I have tried deleting a single day with no change in behavior

 

[ChrisC_3CX]

We would recommend that you contact 3CX Support regarding this case as it will definitely need a more in-depth look to determine what is happening and therefore pinpoint the cause of the issue.

Please do consider submitting a ticket.

 

[ChrisC_3CX]

@c.holloway

One thing I forgot to mention is that the 3CX Instance in question actually falls under the "Enterprise" tier of 3CX deployments so, before contacting our Support team, I highly recommend you do increase the resources as mentioned in our guide to ensure you are running a fully supported configuration.

Do also give it another try once you do so just in case.