vicidial.org

Hi Matt,

In current scenario the time counter does not reset when agent come to Ready mode from Pause mode. If the agent has taken more time than expect say 1min or 2min to dispose the call and than comes to ready mode which gives an impression as if dialer has taken more time to allocate the call to the agent or there is flaw in reporting.

I would request if u can change the code in such a way that whenever agent come to Ready mode from Pause Mode the time counter should reset. That should also reflect in the report so that one can monitor what is the actual idle time due to dialer and how much time an agent is taking in disposing a call.

Regards,
Alex

astguiclient version?

We are working on some different display changes along the lines of what you are mentioning, but simply resetting the timer is a bit more difficult than it seems so we are doing a few different things to try to give better information in the real-time report.

Hi Matt,

Im using 2.0.2 version of VICI Dial.i hope ths change would make the job a lil more easy for the admin and the ops manager.

cheers

Hi Matt, i'm having the same problem with a server, this is the info:

VERSION: 2.0.5-173
BUILD: 90320-0424
Asterisk 1.4.21.2

Doing outbound calls in predictive mode and manual, an average of 20 agents recording always.

The only change i made in this server was activate the auto-pause agent after disposition screen.

The agent go to PAUSE state, and when go to READY state the TIME ON VDAD Report don't resets the time and keeps the value of the PAUSE State.

SVN trunk(2.2.0) resolves this to use any change-in-state as a timer reset on the realtime report.

Thanks Matt, i will try with the trunk version and will post my results.

May i replace only the real-time report php file? Or i need to do a complete reinstallation?

I don't think the new realtime screen will work on an older installation because of the changes in the database.

And you don't need to reinstall, just read and follow the instructions in the UPGRADE doc.

Ok, thanks Matt.

One last question. Is the trunk version recommended for a Production server?

All of our managed clients are running a recent version of SVN trunk in production, so I would say it's safe.