Update XML CDR Extension Summary Queries #5979 #6365
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rebased version of #5979
The queries in the Extension Summary have not been updated for a long time. Many changes have been made to the CDR import script that has changed how calls are counted. As a result, the data population in the extension summary has been wildly inaccurate.
The queries have now been copied from the $sql query output of the xml_cdr page. As such, they are updated to match what a user would see if they were to use basic filters on xml_cdr.
Additionally, the following logic now applies:
We have tested these queries quite extensively for a few months and compared to many different call flow configurations of live data and everything now continues to match quite well.