Fix fake call and discrepancy from cdr and queue_log on duration of answered calls #199
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
in the query that inserts data into report_queue_agents table, the correct row with the answered call data (dst_cnam, billsec, dstchannel, linkedid) was not returned because the result is not ordered, we need the first row, adding sorting by calldate solves the problem.
rows with event (RINGNOASNWER) and data1 (0 or 1000) are fake calls caused by incorrect queue configuration (these are calls that theoretically rang 0 or 1000 milliseconds), we need to eliminate this data before doing the reporting calculations