Page 1 of 1

Meaning of DEAD call

PostPosted: Fri Jul 10, 2009 2:02 am
by saurabh4485
Dear Matt,


I installed vicidial1.2 . when i am executing TIME ON VDAD (per campaign) Report...

I found some users on a DEAD CALL ...What do you mean by DEAD call ????

+------------+--------------------+-----------+----------+-----------------+-----------------+---------+------------+-------+
| STATION | USER | SESSIONID | STATUS | SERVER IP | CALL SERVER IP | MM:SS | CAMPAIGN | CALLS |
+------------+--------------------+-----------+----------+-----------------+-----------------+---------+------------+-------+
| SIP/6003 | 6023 | 8600070 | READY | 192.168.1.2 | | 0:23 | VODAFONE | 34 |
| SIP/6017 | 6028 | 8600057 | READY | 192.168.1.2 | | 0:10 | VODAFONE | 43 |
| Zap/35 | 6020 | 8600068 | READY | 192.168.1.2 | | 0:42 | VODAFONE | 15 |
| Zap/36 | 6004 | 8600065 | READY | 192.168.1.2 | | 0:46 | VODAFONE | 37 |
| SIP/6007 | 6031 | 8600059 | READY | 192.168.1.2 | | 0:13 | VODAFONE | 50 |
| SIP/6021 | 6002 | 8600077 | INCALL A | 192.168.1.2 | 192.168.1.2 | 5:54 | VODAFONE | 29 |
| Zap/33 | 6015 | 8600061 | INCALL M | 192.168.1.2 | | 3:18 | VODAFONE | 33 |
| SIP/6009 | 6025 | 8600056 | DEAD A | 192.168.1.2 | 192.168.1.2 | 5:16 | VODAFONE | 14 |
| Zap/39 | 6007 | 8600063 | INCALL A | 192.168.1.2 | 192.168.1.2 | 2:52 | VODAFONE | 40 |
| SIP/6019 | 6014 | 8600053 | DEAD A | 192.168.1.2 | 192.168.1.2 | 2:34 | VODAFONE | 44 |
| Zap/37 | 6005 | 8600071 | INCALL A | 192.168.1.2 | 192.168.1.2 | 1:18 | VODAFONE | 27 |
| Zap/38 | 6027 | 8600067 | DEAD A | 192.168.1.2 | 192.168.1.2 | 2:26 | VODAFONE | 34 |
| Zap/32 | 6032 | 8600055 | INCALL M | 192.168.1.2 | | 0:57 | VODAFONE | 38 |
| SIP/6020 | 6022 | 8600075 | INCALL A | 192.168.1.2 | 192.168.1.2 | 0:29 | VODAFONE | 29 |
| SIP/6004 | 6021 | 8600076 | INCALL A | 192.168.1.2 | 192.168.1.2 | 0:29 | VODAFONE | 25 |
| SIP/6002 | 6033 | 8600066 | INCALL A | 192.168.1.2 | 192.168.1.2 | 0:10 | VODAFONE | 34 |
| SIP/6005 | 6018 | 8600054 | INCALL A | 192.168.1.2 | 192.168.1.2 | 0:05 | VODAFONE | 23 |
| SIP/6011 | 6016 | 8600060 | PAUSED | 192.168.1.2 | | 83:30 | VODAFONE | 4 |
| SIP/6006 | 6006 | 8600074 | PAUSED | 192.168.1.2 | | 9:19 | VODAFONE | 11 |
| SIP/6026 | 6003 | 8600073 | PAUSED | 192.168.1.2 | | 7:25 | VODAFONE | 33 |
| SIP/6013 | 6001 | 8600052 | PAUSED | 192.168.1.2 | | 6:03 | VODAFONE | 21 |
| SIP/6015 | 6012 | 8600062 | PAUSED | 192.168.1.2 | | 4:35 | VODAFONE | 26 |
| Zap/34 | 6026 | 8600051 | PAUSED | 192.168.1.2 | | 3:30 | VODAFONE | 35 |
| SIP/6018 | 6010 | 8600058 | DISPO | 192.168.1.2 | | 0:12 | VODAFONE | 26 |
| SIP/6001 | 6017 | 8600064 | DISPO | 192.168.1.2 | | 0:19 | VODAFONE | 31 |
+------------+--------------------+-----------+----------+-----------------+-----------------+---------+------------+-------+
25 agents logged in on all servers

PostPosted: Fri Jul 10, 2009 5:15 am
by mflorell
This is not a development question, it is support.

I'm not sure what Vicidial 1.2 is.

a DEAD call in that report is when an agent is still INCALL but the customer has hung up, but they have not gone to the DISPO screen yet.

PostPosted: Fri Jul 10, 2009 8:28 am
by saurabh4485
thanks

PostPosted: Sun Aug 30, 2009 8:24 pm
by gerski
Hello,

I have installed 2.0.5 just now, in AST_timeonVDADall.php sometimes we have dead calls (black) around 2 to 3 agents simultaneously around 1 to 5 3 min and i believe that is INCALL but the customer has already hangup, but in the agent screen they have done the dispo and just wait for another call, do you guys have an idea how to solve it?

PostPosted: Mon Aug 31, 2009 6:23 am
by mflorell
DEAD should only show up while the agent is INCALL and the customer has hung up. How long does it stay like this while the agents are waiting for a new call?

PostPosted: Thu Oct 08, 2009 2:54 pm
by ekaftan
mflorell wrote:DEAD should only show up while the agent is INCALL and the customer has hung up. How long does it stay like this while the agents are waiting for a new call?


Matt: I also have a problem with agents showing up dead. In my case, they show up dead when they park the customer to transfer them to another callcenter.

Can you check if its a bug or something I can fix?

thanks.

PostPosted: Fri Oct 09, 2009 10:03 pm
by mflorell
The park dead bug was fixed last month in SVN trunk.

PostPosted: Sun Oct 11, 2009 10:20 pm
by ekaftan
mflorell wrote:The park dead bug was fixed last month in SVN trunk.


Can I just upgrade from 2.0.5.1 to SVN?

PostPosted: Mon Oct 12, 2009 6:00 am
by mflorell
Yep, just make sure you read and understand all of the items in the UPGRADE document. You will need to make some conf file changes for this upgrade.