Need to "fix" QueueMetrics data when Asterisk Queue Call Redirected via AMI

[eschurke]

We're using an in-house app that allows managers to cherry-pick calls from queue that is performing an AMI channel redirect on the channel that is in queue.

What I've noticed is that those calls which are answered by an agent through AMI redirection are reflected by QueueMetrics as unanswered calls because the Queue App doesn't see the call get answered.

What data should we insert into the MySQL table to reflect the call as 'answered'?

[QueueMetrics]

You should fake the CONNECT  and COMPLETEAGENT lines after the ENTERQUEUE line that should already be there. You can add them at the end of the call if this is easier ( the call will be shown as unanswered in this case). Just keep the same format as of other lines in your queue-log (agent names, etc).

[QueueMetrics]

Also, more than on mysql, I would add the lines to the queue_log itself - this way it is easier to restore from a backup, as you have everything on one place. But you choose.

[eschurke]

Thanks!  We have logrotate setup anyway so if we loose it... we loose it.   

[eschurke]

Just to make sure we've got it right, could you explain uses for data1,data2,data3,unique_row_count for these two verbs?

Thanks!

[QueueMetrics]

CONNECT + wait time
COMPLETEAGENT + wait time + talk time

Qm should not care if the times are wrong, it will recomput ethem from the timestamp.