vicidial.org

Hi Support,

We have issue with realtime report on Vicidial.
It showed the TMA more than 100%.
The TMA is a SLA and the setting i was set at ingroup as standard TMA 1 20sec and TMA 2 30sec.

How come in realtime showed like this.

CALLS TODAY: 99 TMA 1: 101.01% Average Hold time for Answered Calls: 2 TIME: 2022-06-18 10:34:49
DROPS TODAY: 0.000 TMA 2: 101.01% Average Hold time for Dropped Calls: 0
ANSWERS TODAY: 99.000 (Agent non-pause time / Answers) Average Hold time for All Calls: 2
DROP PERCENT: 0.00% PRODUCTIVITY: 1.33


Any idea to solve this issue?

Thanks in advance.

Version: 2.14b0.5
SVN Version: 3607
DB Schema Version: 1661
Vicibox10

After checked in details, our TMA or SLA not accurate due to the table inside database.
It seems the table vicidial_campaign_stats is not update properly and this random happen.
Sometime this update with correct data but sometime it update inaccurate data.
Why this happen? and which cronjob it update for this table?

I setup as a cluster.

1) Welcome to the Party!

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 (10.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... 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 "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. 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) I suspect there are other settings to determine SLA than just time. Disposition may also be involved. Human Answer flag on the dispositions (aka: statuses).