This is what some example data looks like.
- Code: Select all
~5019=30=1=0=6=51=0=0=0=9=72
~5015=0=0=0=0=0=0=0=0=0=0
~5016=0=0=0=0=0=0=0=0=0=0
~5018=0=0=0=0=0=0=0=0=0=0
~5019=31=0=0=6=49=0=0=0=10=72
~5015=0=0=0=0=0=0=0=0=0=0
~5016=0=0=0=0=0=0=0=0=0=0
~5018=0=0=0=0=0=0=0=0=0=0
~5019=31=0=0=6=49=0=0=0=10=72
~5015=0=0=0=0=0=0=0=0=0=0
~5016=0=0=0=0=0=0=0=0=0=0
~5018=0=0=0=0=0=0=0=0=0=0
~5019=31=65535=0=6=49=0=1=38=10=72
~5015=0=0=0=0=0=0=0=0=0=0
~5016=0=0=0=0=0=0=0=0=0=0
~5018=0=0=0=0=0=0=0=0=0=0
~5019=32=65535=0=6=48=0=0=0=11=72
~5015=0=0=0=0=0=0=0=0=0=0
~5016=0=0=0=0=0=0=0=0=0=0
~5018=0=0=0=0=0=0=0=0=0=0
On the first line you can see the Group and then the Number of calls followed by the amount of unanswered calls. Ruby works out the difference between the values every-time it receives the next intervals' data and then reports on that. We have seen the value jump to the max value possible and then back to 0 in some very rare cases. The Max value is 65535. Ruby then works out the difference and sees that that the number of calls from the previous interval is 65535 and reports on this. the value can't go any higher and will then stay on 65535 until it is reset. When the value is reset, it goes back down to 0. Now the difference is 65535 again. This value is added to the number of calls and that is 131070 now.
Recommendations:
- Make sure that you try and reset these values on a regular bases that it doesn't get to 65535. You should be able to configure the PBX to reset it on a daily bases automatically or even after each reported interval.
- If this problem does occur, you can remove 131070 from your total to get the actual value.