31
Running QueueMetrics / Re: Is it possible to see Extension being called as it's ringed?
« on: April 12, 2011, 16:18:20 »
So let's add it as a quick feature (to be enhanced in future version) and assign it a bug #. 
QueueMetrics professional call center suite for the Asterisk PBX
News:
Welcome to the new forum!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
32
Running QueueMetrics / Re: Is it possible to see Extension being called as it's ringed?
« on: April 11, 2011, 16:10:14 »
But it's also so easy to add an:
to incoming context and so it adds the Ringing line to Queue log. This can be easy work-around rather than reading events and only other change is to be made on the java-script running the dashboard to pick this up. Probably if the 5 second is lowered to 1 or 2 seconds then this feature would make more sense as it's time sensitive.
-Bruce
Code: [Select]
exten = _X.,n,System(echo "Ringing" >> /var/log/asterisk/queue_log)to incoming context and so it adds the Ringing line to Queue log. This can be easy work-around rather than reading events and only other change is to be made on the java-script running the dashboard to pick this up. Probably if the 5 second is lowered to 1 or 2 seconds then this feature would make more sense as it's time sensitive.
-Bruce
33
QueueMetrics news / Re: QueueMetrics 1.7.0 released
« on: April 09, 2011, 16:39:43 »
Is there a problem with the QM repository servers? Low bandwidth? or maybe your internet connection is no good.
The only other way would be to do a wget for the rpm files and do an "rpm -ivh" which I am sure should take around the same time with wget if there is an internet issue on either side.
The only other way would be to do a wget for the rpm files and do an "rpm -ivh" which I am sure should take around the same time with wget if there is an internet issue on either side.
34
Running QueueMetrics / Re: Is it possible to see Extension being called as it's ringed?
« on: April 09, 2011, 16:37:12 »
Not sure what your question is but if you are asking if an event is generated then I should say with a resounding "Yes".
SIP ends always echo back Ringing stage and also Asterisk shows in channelstatus() and generates a Ringing event for it. So, it exists in Asterisk logs and AMI events.
SIP ends always echo back Ringing stage and also Asterisk shows in channelstatus() and generates a Ringing event for it. So, it exists in Asterisk logs and AMI events.
35
Running QueueMetrics / Re: Is it possible to see Extension being called as it's ringed?
« on: April 08, 2011, 15:20:16 »
That's why maybe QM should start reading EVENTs. I always wondered why you chose Queue Logs?
Is it because different versions of Asterisk change Events output and it would have been ton of work to keep up?
Thanks
Is it because different versions of Asterisk change Events output and it would have been ton of work to keep up?
Thanks
36
Running QueueMetrics / Best way to implement Outbound Campaign calls using FreePBX?
« on: April 06, 2011, 08:40:24 »
Hi Everyone,
This is the only reference I see to outbound campaign calls. The only reason we want to use outbound campaign is because we want a reference to the recordings and also to make life easier for agent so they don't have to press PAUSE each time they make an outbound call.
http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s23.html#_defining_outbound_queues_campaigns
The reference above very briefly touches on creating a dial-plan. It doesn't take into effect the complexity of FreePBX and how the outbound dialing rules in it's Outbound Routes might effect this.
Can someone who has configured FreePBX (PBXinaflash, Elastix, Trixbox) along with QM for outbound campaigns please shed some light as to which files were tampered and what dial-plans you put in place to least tamper with the FreePBX ecosystem.
Would it be possible to do this using Custom string and Custom trunks at all? (good to keep things in the GUI all the time - better administration possible)
Much appreciated. Thanks
This is the only reference I see to outbound campaign calls. The only reason we want to use outbound campaign is because we want a reference to the recordings and also to make life easier for agent so they don't have to press PAUSE each time they make an outbound call.
http://queuemetrics.com/manuals/QM_UserManual-chunked/ar01s23.html#_defining_outbound_queues_campaigns
The reference above very briefly touches on creating a dial-plan. It doesn't take into effect the complexity of FreePBX and how the outbound dialing rules in it's Outbound Routes might effect this.
Can someone who has configured FreePBX (PBXinaflash, Elastix, Trixbox) along with QM for outbound campaigns please shed some light as to which files were tampered and what dial-plans you put in place to least tamper with the FreePBX ecosystem.
Would it be possible to do this using Custom string and Custom trunks at all? (good to keep things in the GUI all the time - better administration possible)
Much appreciated. Thanks
37
Running QueueMetrics / Is it possible to see Extension being called as it's ringed?
« on: April 06, 2011, 07:03:15 »
Hello,
Am I missing something or is the Wall-board not capable of showing what Extension is being ringed? As a call comes in, I see the call in Wait and I hear an extension ringing but I can't see the extension number on the Wall-Board.
Am I missing a parameter in the configuration file or is it not supported at all?
I think this adds a very much needed feature to the system because one can literally see which Agent is lazy and not picking up the phone specially in a system where Agents do not have a time and they must pick up a call. This also helps with troubleshooting calls that are lost or not picked up.
Currently Wall-board only shows Extension number if a call is CONNECTED and ANSWERED and not when it's ringing.
Please shed some light on it.
Thanks
Am I missing something or is the Wall-board not capable of showing what Extension is being ringed? As a call comes in, I see the call in Wait and I hear an extension ringing but I can't see the extension number on the Wall-Board.
Am I missing a parameter in the configuration file or is it not supported at all?
I think this adds a very much needed feature to the system because one can literally see which Agent is lazy and not picking up the phone specially in a system where Agents do not have a time and they must pick up a call. This also helps with troubleshooting calls that are lost or not picked up.
Currently Wall-board only shows Extension number if a call is CONNECTED and ANSWERED and not when it's ringing.
Please shed some light on it.
Thanks
38
QueueMetrics news / Re: QueueMetrics 1.7.0 released
« on: March 24, 2011, 03:29:25 »
Hello,
Great to know about all the upgrades. I just browsed and noticed that it's missing the AJAX real-time Wall-board. The non-ajax wall-board is way too plain. Can we have the Ajax wall-board still?
Regards
Great to know about all the upgrades. I just browsed and noticed that it's missing the AJAX real-time Wall-board. The non-ajax wall-board is way too plain. Can we have the Ajax wall-board still?
Regards
39
General Asterisk configuration / Re: Something weired with Queue call distribution - Why is there unfair call distri?
« on: February 03, 2011, 16:27:10 »
Thanks for the input.
1- But is that normal behavior to call every 5 seconds? Of course the two extensions were on other calls so why call them every 5 seconds?
2- Why didn't the second call do that? It also waited fro 10 minutes and it only attempted the call once and that is only after 10 minutes.
3- What does the 1000 at the end of lines like this mean: "1296500115|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000"
4- What other logs can I look into to further investigate this?
Thanks again,
1- But is that normal behavior to call every 5 seconds? Of course the two extensions were on other calls so why call them every 5 seconds?
2- Why didn't the second call do that? It also waited fro 10 minutes and it only attempted the call once and that is only after 10 minutes.
3- What does the 1000 at the end of lines like this mean: "1296500115|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000"
4- What other logs can I look into to further investigate this?
Thanks again,
40
General Asterisk configuration / Re: Something weired with Queue call distribution - Why is there unfair call distri?
« on: February 03, 2011, 00:27:02 »
Hello,
All right so I did a search and found the unique call id "1296498905.68292" you requested and run a search for it in queue_log file. Then I also did a search for the other number which was answered unfairly sooner and that is also pasted at the bottom here.
First, the CLID 7777777777 that was waiting 20 minutes and should have been answered before the other number:
And here is the 4444444444 number which waited only 10 minutes and got through:
Why do I have only three lines in queue_log for the other number and so many lines for the first number?
Obviously there are so many attempts on the first number to the two extension 367 and 370 but since they were on call it comes back busy. But for the second number all I see is only three lines of queue_log corresponding to call id "1296498989.68324". Which behavior is normal first of all?
It would be greatly appreciated if you can clarify how the Queue in Asterisk works. Does it have to continuously ring and get BUSY or does Asterisk come back and tells the Queue that "hey there is an open extension waiting for you" which is what happened in second call.
Thanks
All right so I did a search and found the unique call id "1296498905.68292" you requested and run a search for it in queue_log file. Then I also did a search for the other number which was answered unfairly sooner and that is also pasted at the bottom here.
First, the CLID 7777777777 that was waiting 20 minutes and should have been answered before the other number:
Code: [Select]
1296498939|1296498905.68292|498|NONE|ENTERQUEUE||7777777777
1296499664|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499677|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499677|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499682|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499682|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499687|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499688|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|1000
1296499693|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499693|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499698|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499698|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499703|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499703|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499709|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499709|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499714|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499714|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499719|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499719|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499725|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499725|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499730|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499730|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499735|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499735|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499741|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499741|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499746|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499746|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499751|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499751|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499757|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000
1296499757|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|1000
1296499769|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499769|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499774|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499774|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499779|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499779|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499785|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499785|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499790|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499790|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499795|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499795|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499801|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499801|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499806|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499806|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499811|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499811|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499817|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499817|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499822|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499822|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499827|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499827|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499833|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499833|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499838|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499838|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499843|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499843|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499848|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499849|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000
1296499861|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499861|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499866|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499866|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499871|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499871|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499877|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499877|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499882|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499882|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499888|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|1000
1296499888|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000
1296499893|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499893|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499898|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499898|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499903|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499903|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499909|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499909|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499914|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499914|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499919|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499919|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499925|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499925|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499930|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499930|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499935|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499935|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499941|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499941|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499953|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499953|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499958|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499958|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499963|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499963|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499969|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499969|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499974|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499974|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499979|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499979|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499985|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499985|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499990|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499990|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296499995|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296499995|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500001|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|1000
1296500001|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000
1296500006|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500006|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500011|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500011|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500017|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|1000
1296500017|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000
1296500022|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500022|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500027|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500027|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500032|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500033|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000
1296500045|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500045|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500050|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500050|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500055|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500055|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500061|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500061|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500066|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500066|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500071|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500071|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500077|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500077|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500082|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500082|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500088|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|1000
1296500088|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000
1296500093|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500093|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500098|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500099|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000
1296500104|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500104|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500109|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500109|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500114|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500115|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|1000
1296500120|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500120|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500125|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500125|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500137|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500137|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500143|1296498905.68292|498|Local/370@from-internal/n|RINGNOANSWER|0
1296500143|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500148|1296498905.68292|498|Local/362@from-internal/n|RINGNOANSWER|0
1296500148|1296498905.68292|498|Local/367@from-internal/n|RINGNOANSWER|0
1296500150|1296498905.68292|498|Local/370@from-internal/n|CONNECT|1211|1296500148.69383
1296500156|1296498905.68292|498|Local/370@from-internal/n|COMPLETECALLER|1211|6|3And here is the 4444444444 number which waited only 10 minutes and got through:
Code: [Select]
1296499034|1296498989.68324|498|NONE|ENTERQUEUE||4444444444
1296499678|1296498989.68324|498|Local/367@from-internal/n|CONNECT|644|1296499676.68591
1296499761|1296498989.68324|498|Local/367@from-internal/n|COMPLETEAGENT|644|83|5
Why do I have only three lines in queue_log for the other number and so many lines for the first number? Obviously there are so many attempts on the first number to the two extension 367 and 370 but since they were on call it comes back busy. But for the second number all I see is only three lines of queue_log corresponding to call id "1296498989.68324". Which behavior is normal first of all?
It would be greatly appreciated if you can clarify how the Queue in Asterisk works. Does it have to continuously ring and get BUSY or does Asterisk come back and tells the Queue that "hey there is an open extension waiting for you" which is what happened in second call.
Thanks
41
General Asterisk configuration / Something weired with Queue call distribution - Why is there unfair call distri?
« on: January 31, 2011, 20:35:23 »
Hi Everyone,
I have the Queues setup in FreePBX to Leastrecent strategy. I have a problem that I see a call that was waiting only 10 minutes was picked up before a call that was waiting for more than 20 minutes. Following is the records from Queuemetrics and FreePBX:
QueueMetrics records:
Queue Russian is 498 by number. As you can see Caller number 4444444444 was waiting for 20 minutes and entered the queue before Caller number 7777777777 and yet it was answered 10 minutes after the Caller 444444444. In fact 7777777777 should have been answered first.
As per above FreePBX reports I don't also see any attempts on other extensions so it is not a case of agent not picking up the phone. Both calls were picked up with the first attempt. Of course this is a very busy queue as you can see with the wait times but when an extension becomes available it should be assigned to the longest waiting call shouldn't it?
Any clarifications would be appreciated.
Following is how the queue is setup which is Leastrecent for strategy:
Thanks,
I have the Queues setup in FreePBX to Leastrecent strategy. I have a problem that I see a call that was waiting only 10 minutes was picked up before a call that was waiting for more than 20 minutes. Following is the records from Queuemetrics and FreePBX:
QueueMetrics records:
Code: [Select]
Date Caller Queue Wait Duration Pos. Disconnection Handled by Attempts
01/31 - 13:37:14 4444444444 Russian 10:44 1:23 5 Agent Agent/367 1
01/31 - 13:35:39 7777777777 Russian 20:11 0:06 3 Caller Agent/370 1
Corresponding FreePBX records:Code: [Select]
Calldate Channel Source Clid Dst Disposition Duration
2011-01-31 13:47:56 Local/367@... 4444444444 "M11:RuQ: 44444444444" <44444444444> 367 ANSWERED 01:25
2011-01-31 13:36:29 Zap/6-1... 4444444444 "RuQ: 44444444444" <44444444444> 498 ANSWERED 12:52
2011-01-31 13:55:48 Local/370@... 7777777777 "M21:RuQ: 7777777777" <7777777777> 370 ANSWERED 00:08
2011-01-31 13:35:05 Zap/3-1... 7777777777 "RuQ: 7777777777" <7777777777> 498 ANSWERED 20:51Queue Russian is 498 by number. As you can see Caller number 4444444444 was waiting for 20 minutes and entered the queue before Caller number 7777777777 and yet it was answered 10 minutes after the Caller 444444444. In fact 7777777777 should have been answered first.
As per above FreePBX reports I don't also see any attempts on other extensions so it is not a case of agent not picking up the phone. Both calls were picked up with the first attempt. Of course this is a very busy queue as you can see with the wait times but when an extension becomes available it should be assigned to the longest waiting call shouldn't it?
Any clarifications would be appreciated.
Following is how the queue is setup which is Leastrecent for strategy:
Thanks,
42
Running QueueMetrics / Re: How to get a report of a pause code only?
« on: January 18, 2011, 16:32:20 »
Actually, "Ag. Dt." tab when doing a custom report is the search for all session types and the pause codes. It includes all the data in PAUSE codes.
-Bruce
-Bruce
43
Running QueueMetrics / Re: Bug #1202 - Agent MUST set a pause reason - STILL AN ISSUE
« on: January 18, 2011, 16:30:35 »
That parameter does not exist in the configurations.properties file.
I added it and it works like a charm. Thank you.
Are you thinking of embedding the configuration properties on the Admin settings page yet? It would be very handy if you give all parameter radio-check buttons and also provide a Queuemetrics restart button from the GUI interface. Transferring parameters should take much time. A simple php page would do and will bring a lot of good.
I added it and it works like a charm. Thank you.
Are you thinking of embedding the configuration properties on the Admin settings page yet? It would be very handy if you give all parameter radio-check buttons and also provide a Queuemetrics restart button from the GUI interface. Transferring parameters should take much time. A simple php page would do and will bring a lot of good.
44
Running QueueMetrics / Re: Bug #1202 - Agent MUST set a pause reason - STILL AN ISSUE
« on: January 17, 2011, 17:46:05 »
Hello,
Anything to this?
Anything to this?
45
Running QueueMetrics / Re: Bug #1202 - Agent MUST set a pause reason - STILL AN ISSUE
« on: January 15, 2011, 00:24:06 »
Hello,
I have not. Where is that found?
I am afraid you are not getting the point. It's described in this post and agreed by you:
http://forum.queuemetrics.com/index.php?topic=1118.0
Or there is a slight chance I am missing a parameter in configuration.properties file even though I looked it all over.
Thanks
I have not. Where is that found?
I am afraid you are not getting the point. It's described in this post and agreed by you:
http://forum.queuemetrics.com/index.php?topic=1118.0
Or there is a slight chance I am missing a parameter in configuration.properties file even though I looked it all over.
Thanks