Vicidial showing wrong Calls count for agents in realtime

[osib]

Hi
In the real time screen the calls count of agents are wrong as per below details

CALLS TODAY: 950
VICIDIAL: Agents Time On Calls Campaign: |CCUN| 2015-11-17 09:51:50
+----------------+------------------------+-----------+----------+---------+------------+-------+------+------------------
| STATION | USER SHOW ID INFO | SESSIONID | STATUS | MM:SS | CAMPAIGN | CALLS | HOLD | IN-GROUP
+----------------+------------------------+-----------+----------+---------+------------+-------+------+------------------
| 7476@default | Kunjbiha + | 8600057 | INCALL I | 3:37 | CCUN | 26703 | 0 |1 Inbound
| 7490@default | Kumar + | 8600058 | INCALL A | 1:03 | CCUN | 28875 |
| 7480@default | Faleiro + | 8600063 | INCALL A | 0:39 | CCUN | 33131 |
| 7474@default | Lyngdoh + | 8600068 | INCALL I | 0:13 | CCUN | 21740 | 0 | 1 Inbound
+----------------+------------------------+-----------+----------+---------+------------+-------+------+------------------

How can I reset agent calls count every day

Please help

Thanks

[striker]

make sure you are shutting down the server after the Timeclock End Of Day time


check what time you have set for Timeclock End Of Day:
Admin- System Settings - Timeclock End Of Day:

enter the time your calling shift finishes or before shutdown time.

[osib]

Hi Striker
Timeclock End of Day: 0000
The server restarts at: 0030
Still the issue persists

Can it be solved without restarting the server every day

Thanks

[osib]

Hi
Can someone help me on this as if I setup new dialler from scratch then Calls counts in real-time screen is fine but when I upgrade vicidial still the issue persists. Formatting and setting up all diallers will take lots of time...

Thank you

[williamconley]

Hi
Can someone help me on this as if I setup new dialler from scratch then Calls counts in real-time screen is fine but when I upgrade vicidial still the issue persists. Formatting and setting up all diallers will take lots of time...

Thank you

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 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) And based on your comment, you should post the version of Vicidial that was installed, then the version you upgraded to ... AND the method you used to upgrade. Did you follow the instructions in /usr/src/astgcuiclient/trunk/UPGRADE? (And did you "svn up" in /usr/src/astgcuiclient/trunk before you began?)

[osib]

Asterisk 1.8.23.0-vici
Debain 7.9
VICIDIAL VERSION: 2.12-543a
BUILD: 160313-0756
Version: 2.12b0.5
SVN Version: 2491
DB Schema Version: 1456

[osib]

Hi William
I followed all the steps but still don't understand why its not working.

If I install fresh vicidial and do svn update it works but in old one it doesn't (with same version of astguiclient and vicidial source). The old one has records in db so while updating the tables and records, it takes time. Would presence of records matter?

Thanks

[williamconley]

... you should post the version of Vicidial that was installed, then the version you upgraded to ... AND the method you used to upgrade....

You keep asking vague questions with no details. All I could do is give vague answers. Probably better to switch to technical mode. *)

[mflorell]

Make sure you have the System Settings "Active Voicemail Server" set to a valid Asterisk server on your cluster.

[osib]

Thank you mflorell
It works now

[Kelerion]

Hi guys,

I have the same issue... so have tried this voicemail thing..

Will have to wait till tomorrow to see if it works but just out of curiousity I was wondering.... why?... why would that have anything to do with it?

This is just pure curiosity... not a questioning...

Thanks

Kel.

[Kelerion]

ok...update...that didn't work... didn't even have to wait till the timeclock kicked in...

couple of the agents just suddenly jumped to over 3000 calls (but not all of them)

I'd already run a "update vicidial_live_agents set calls_today=0;" first thing this morning just to reset it today to check.

So here's the setup...

Single server...single DB... simple setup as per Striker's Centos Install.

I always keep up with the current SVN so as of this morning:

VERSION: 2.12-564a
BUILD: 160809-1339
Centos 6.7
Asterisk 1.8.23.0-vici

Server has been running a couple of years now and we don't tend to have many issues... generally rock-solid... just little strange things like this.

I seem to remember up till a few months ago this all being correct... so not sure if somethings changes since then to cause it.

[williamconley]

Then your best bet could be to perform a fresh install with Vicibox 7's latest iso, and then put your DB into it and upgrade the sql (which likely won't be much of an upgrade, since you've been keeping up).

Then you'll have a shiny new machine without the debate of whether there's an installation issue.

Do note that this method WILL require you to revisit your server settings and possibly your system settings. I've even taken the extra step a few times of bringing these two tables back from the fresh install to avoid bothering with finding the differences (since the fresh install with have a functional record for each). Then quick adjustments for "known values" only is all that's needed (like MAX calls per second, which is often unique to the carrier/client requirements).