General and Support topics relating to ViciDialNow and GoAutoDial ISO installers
Moderators: enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, s0lid
by dexterity » Sat Jun 19, 2010 4:44 pm
are the following true?
wait_epoch-pause_epoch = pause_sec
talk_epoch-wait_epoch = wait sec
dispo_epoch - talk_epoch = talk_sec
if they are all true, what will be the possible reasons why there are entries in the table wherein it does not hold true?
is it safe to assume that the stages of the call will be
queue => talk => dispo ?
or
queue => talk => dead (if any) => dispo?
there are entries in my database wherein dead_epoch is less than dispo_epoch.
btw, what is dead_sec?
----------------
vicidialnow 1.3
upgraded to 2.2 SVN
VERSION: 2.2.1-237
BUILD: 100510-2015
quad-core 2.4 xeon
4GB RAM
500 GB drive
-
dexterity
-
- Posts: 6
- Joined: Fri May 01, 2009 10:58 pm
by dexterity » Fri Jun 25, 2010 7:09 pm
anyone?
-
dexterity
-
- Posts: 6
- Joined: Fri May 01, 2009 10:58 pm
by mflorell » Fri Jun 25, 2010 8:25 pm
We've been over this a few times. And a lot of changes were made in 2.2.1 to make it more accurate, but I'm not really sure of everything you are asking, please rephrase separate questions in more detail.
Also, are these entries in your crontab:
33 * * * * /usr/share/astguiclient/AST_cleanup_agent_log.pl
50 0 * * * /usr/share/astguiclient/AST_cleanup_agent_log.pl --last-24hours
-
mflorell
- Site Admin
-
- Posts: 18384
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
-
by dexterity » Tue Jun 29, 2010 1:53 am
fresh sample snippet form the database.
+---------------------+-------------+-----------+------------+----------+------------+----------+-------------+-----------+--------+----------+------------+----------+
| event_time | pause_epoch | pause_sec | wait_epoch | wait_sec | talk_epoch | talk_sec | dispo_epoch | dispo_sec | status | comments | dead_epoch | dead_sec |
+---------------------+-------------+-----------+------------+----------+------------+----------+-------------+-----------+--------+----------+------------+----------+
| 2010-06-29 02:22:40 | 1277792560 | 9 | 1277792569 | 3 | 1277792572 | 18 | 1277792583 | 5 | MISC | MANUAL | NULL | 0 |
| 2010-06-29 02:23:08 | 1277792588 | 645 | 1277793233 | 3 | 1277793236 | 26 | 1277793251 | 5 | MISC | MANUAL | NULL | 0 |
| 2010-06-29 02:34:16 | 1277793256 | 85 | 1277793341 | 2 | 1277793343 | 128 | 1277793408 | 4 | MISC | MANUAL | NULL | 0 |
| 2010-06-29 02:36:52 | 1277793412 | 36 | 1277793448 | 4 | 1277793452 | 78 | 1277793493 | 3 | MISC | MANUAL | NULL | 0 |
| 2010-06-29 02:38:16 | 1277793496 | 34 | 1277793530 | 3 | 1277793533 | 35 | 1277793552 | 3 | MISC | MANUAL | NULL | 0 |
+---------------------+-------------+-----------+------------+----------+------------+----------+-------------+-----------+--------+----------+------------+----------+
the 3rd, 4th, and 5th rows should have values just in the area of half of that.
wait_sec should have been zero since there are no waiting calls. I'm thinking it becomes the time it takes for the call to connect for a manual call.
3rd and 4th I used the the park call button.
1st, 2nd, and 5th, are straight manual calls.
33 * * * * /usr/share/astguiclient/AST_cleanup_agent_log.pl <-- on cron
50 0 * * * /usr/share/astguiclient/AST_cleanup_agent_log.pl --last-24hours <-- not on cron, added now
-
dexterity
-
- Posts: 6
- Joined: Fri May 01, 2009 10:58 pm
by mflorell » Tue Jun 29, 2010 7:04 am
The vicidial_agent_log shows agent activity, not based upon the call, so it will not show the wait_sec of the customer, it shows the wait_sec of the agent.
Park call time is not logged.
-
mflorell
- Site Admin
-
- Posts: 18384
- Joined: Wed Jun 07, 2006 2:45 pm
- Location: Florida
-
Return to ViciDialNow - GoAutoDial
Who is online
Users browsing this forum: No registered users and 89 guests