vicidial pause code Report

[ivschakravarthi]

Hello,

Vicidial 2.2.1 ,asterisk 1.4.15,single server, Centos5.5 ,No telephony card,No cluster
The above is my configuration.

In the Agent Performance Report,what does the Pause code Report statistics display.
In which scenarios these fields get updated and in which scenario it wont get updated.
There is a report column "TOTAL" and what does it mean?
I have some agents whose "TOTAL" time is more than 24 hours [26 hours is the max value i have seen].
Why it went to more than 24 hours and in what scenario it is going?


Regards,
chak

[williamconley]

1) Welcome to the party!

2) Newbie suggestions (I see you are trying to post your specs, but you have missed your installation method ... so you get the whole schpiel in case you missed anything else ...):

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) Post a sample with headers from the report and ask ... as a rule, however, you'll need to be sure you include the "criteria" that you used in the report (ie: did you supply a date range? campaign filter ... what did you ask for in the report ...?)

[ivschakravarthi]

Hi,
Below is the agent pause code Report ,i have only one campaign and i have selected only one date range
which is displaying 24 hrs plus of TOTAL time for one use.



Below is the user_stats report for that particular user for that day which shows 22HRs
But in the Agent login/log out report in the user_stats Page,it is displaying only 6 Hours 40 mins as LOGIN duration




As mentioned i have only campaign and 1 in group.so ,no concept of wrong filtering the data.
If the agent itselfs is logged for 6 hours 40 mins duration,how can he get 22 Hrs and 24hrs in the other reports?
Major issue is how the agent is crossing 24 hours plus in the pause code report when we have only 24 hours in a day.
Some agents are going upto 26 hours.

Regards,
chak

[williamconley]

I'd love to tell you, but there is no data in your post which could be checked. No images. No copy/pasted report information. No url (which may at least show the precise information used to gather the results). Nada.

[ivschakravarthi]

Dear william,
I have updated my previous post with the image urls placed.
Request you to check once

Regards,
Chak

[williamconley]

We're getting closer. but no column headers on one report and no url on any of them means I still have no idea where this information came from. Free support = i'm not able to take the time to go look this stuff up. so all I can say is, give me all the information that is hidden and perhaps I can form an opinion. Happy to Help, but ...

You can also try upgrading to the latest version of vicidial which has been known to clean out plenty of "bugs" in various areas.

[ivschakravarthi]

Hi,
i have edited my post with headers included.Hope it might be helpful for me to assist.

[williamconley]

you'll have to find the underlying data from the sql tables. it is possible that the agent turned off his computer or closed a browser window instead of logging off or dispositioning a call .. but until you find the db entries generating the data, it's all just guesses.

[ivschakravarthi]

I have don some analysis and i found that abnormality is due to the disposition time of the last call of the agent.
Agent took around 58952 seconds to disposition his last call which he had taken at 7:06 PM


But when i look into his Login /Log out Report the logout of the agent is recorded as 7:27 PM


We cant think that agent didnt disposition the call properly because a log out event is captured for the day.
Had one more about the login and log out capture events.
In the above you can observe double logout events were captured without respective login events.

[williamconley]

I have don some analysis and i found that abnormality is due to the disposition time of the last call of the agent.
Agent took around 58952 seconds to disposition his last call which he had taken at 7:06 PM


But when i look into his Login /Log out Report the logout of the agent is recorded as 7:27 PM


We cant think that agent didnt disposition the call properly because a log out event is captured for the day.
Had one more about the login and log out capture events.
In the above you can observe double logout events were captured without respective login events.

perform a test yourself and just "close the window" while you're in a call or paused and see if you get similar results.

then install Vicibox.com's .iso and try it again to see if the error is gone. if so ... upgrade!