1
Running QueueMetrics / Re: Question related to AvgRing (RT tichet #1323)
« on: October 06, 2011, 14:20:10 »
This is not our case - we are running RRMEMORY queues.
Also, almost all CONNECT events are with ringtime=0.
As I have mentioned in the initial post there are almost no RINGNOANSWER events in the queue_log (18 from a total of 728 CONNECTED calls).
Our point of view - expressed on the support ticket as well - is that the RingTime is not computed correctly. This should be done on the "ringtime" info from RINGNOANSWER and CONNECT events. From the data we have in the demo sessions we performed extensively this week it looks the RingTime is computed somehow else.
Best regards,
Ioan
Code: [Select]
[root@host66 tools]# grep -c RING /var/log/asterisk/queue_log
18
[root@host66 tools]# grep -c CONNECT /var/log/asterisk/queue_log
728
Also, almost all CONNECT events are with ringtime=0.
Code: [Select]
[root@host66 tools]# grep CONNECT /var/log/asterisk/queue_log | grep -c "|0$"
249
As I have mentioned in the initial post there are almost no RINGNOANSWER events in the queue_log (18 from a total of 728 CONNECTED calls).
Our point of view - expressed on the support ticket as well - is that the RingTime is not computed correctly. This should be done on the "ringtime" info from RINGNOANSWER and CONNECT events. From the data we have in the demo sessions we performed extensively this week it looks the RingTime is computed somehow else.
Best regards,
Ioan