Wait time always 0

[cursor]

I am setting up a new Queuemetrics installation with Asterisk 11.4 and Queuemetrics 13.04.02.  Everything seems to be working fine except that when I go to a report the wait time for all calls is always 0:00.  The duration is correct so I have no idea why wait time is not displayed properly.  Anything I need to tweak in the configuration?  The agent realtime page does show the correct wait time so why the difference?

[marcos]

Hi.

Could you provide us a short piece of your queue_log file where is possible to see the events associated to a single call?

Best regards,
Marco Signorini.

[cursor]

Here is a queue_log entry for a call:

1372782526|1372782526.403|FEPADE|NONE|ENTERQUEUE||5517924703|1
1372782529|1372782526.403|FEPADE|SIP/103|CONNECT|3|1372782526.404|3
1372782591|1372782526.403|FEPADE|SIP/103|COMPLETECALLER|3|62|1

Here is the call detail from Queuemetrics:

Asterisk Call ID:       1372782526.403
Date and time:       07/02 - 11:28:46
Queue:       FEPADE [fepade]
Caller ID:       5517924703
Handled by:       Agente 3 (103)
Duration:       62 sec.
Time in IVR before queueing:       0 sec.
Waiting time:       0 sec.
Original position       # 1
Disconnection cause:       Caller disconnected
Transferred to:       
Attempts:       1
Last Failed Attempt:       -
Bridged Channel:       1372782526.404
Stints:       1
URL:       
Status code:       
Srv       
DNIS       
IVR selection       
- 1372782526.403.wav

As you can see IVR and Wait time are 0 for the call but the log entry says 3.  As I mentioned before the agent page does have the correct wait time.  Here is the information from the database on the same call:

+-----------+------------+----------------+--------+---------+----------------+-------+----------------+-------+-------+-------+----------+------------------+
| partition | time_id    | call_id        | queue  | agent   | verb           | data1 | data2          | data3 | data4 | data5 | serverid | unique_row_count |
+-----------+------------+----------------+--------+---------+----------------+-------+----------------+-------+-------+-------+----------+------------------+
| P001      | 1372782526 | 1372782526.403 | FEPADE | NONE    | ENTERQUEUE     |       | 5517924703     | 1     |       |       |          |                1 |
| P001      | 1372782529 | 1372782526.403 | FEPADE | SIP/103 | CONNECT        | 3     | 1372782526.404 | 3     |       |       |          |                1 |
| P001      | 1372782591 | 1372782526.403 | FEPADE | SIP/103 | COMPLETECALLER | 3     | 62             | 1     |       |       |          |                1 |
+-----------+------------+----------------+--------+---------+----------------+-------+----------------+-------+-------+-------+----------+------------------+

[cursor]

I just grabbed the queue_log file and did a new setup on another server and all reports give me the correct wait time.  I am using the same version installed via yum and loway.repo.  I really do not know what the possible reason for the problem is but I need to fix the problem in the production server without nuking everything.

[QueueMetrics]

You sure you are parsing the very same dataset?

[cursor]

I found the problem.  When the Queuemetrics installation was done the persona that installed it rand the database init twice and there was some duplicate information in many tables.  If I take the queue_log table to another Queuemetrics server I do get all the proper stats.

[QueueMetrics]