Two use-cases where autofill=no is desirable:
1) If it's important that you answer your callers in strict order (i.e.
in order to meet estimated wait time commitments etc).
2) If your queue members/agents are local channels (as local channels
are always available, so call attempts will be
With regard to (1), yes, very good point there and certainly reason
enough to leave it alone. I had completely forgotten about a use case
like that.
With regard to (2), I'm pretty sure there's been work done in the
recent past to make chan_local more state aware so that this might not
be
Hey,
I just found out today that it doesn't work on Asterisk 1.4.19 (at
least for realtime queues) if you have autofill=yes in queues.conf.
However it works if you add it in queue settings for each queue, for
realtime that would be
ALTER TABLE queue_table ADD COLUMN autofill TINYINT(1) UNSIGNED
Two use-cases where autofill=no is desirable:
1) If it's important that you answer your callers in strict order (i.e.
in order to meet estimated wait time commitments etc).
Not always the case. Let's look at multiple queue assignment where agents
have skills (logged in) to multiple queues.
Yup, I am using realtime queue. Do you mean the global setting in
queue.conf is useless and you have to set every thing in each queue to
activate the settings? If it is true, does it also apply to other
realtime settings?
On Tue, Apr 15, 2008 at 8:21 PM, Atis Lezdins [EMAIL PROTECTED] wrote:
Anyone can update me about the queue sticking by a caller? Is it
solved in version 1.4.x? How?
On Sat, Apr 12, 2008 at 9:42 AM, Rilawich Ango [EMAIL PROTECTED] wrote:
Do you mean autofill works in 1.4.x? But it doesn't work even I set it.
On Fri, Apr 11, 2008 at 11:07 AM, BJ Weschke
BJ Weschke wrote:
Rilawich Ango wrote:
Thanks. I have checked that the queue.conf. I keep the default
setting as autofill=yes in my tests. That's mean even autofill=yes,
the 1st caller will still stick the whole queue.
asterisk version : 1.4.18
--queue.conf--
; AutoFill Behavior
;
Do you mean autofill works in 1.4.x? But it doesn't work even I set it.
On Fri, Apr 11, 2008 at 11:07 AM, BJ Weschke [EMAIL PROTECTED] wrote:
Rilawich Ango wrote:
Thanks. I have checked that the queue.conf. I keep the default
setting as autofill=yes in my tests. That's mean even
HI all,
I have set up a queue with 2 members (A B). 1st call is waiting
in the queue and a queue member A is ringing but don't take the call.
Member A keeps ringing. Then 2nd call is also get into the queue but
I found that queue member B doesn't ring. That's mean member B is
available to
Rilawich Ango Thursday, April 10, 2008 3:28 AM
I have set up a queue with 2 members (A B). 1st call is waiting
in the queue and a queue member A is ringing but don't take the call.
Member A keeps ringing. Then 2nd call is also get into the queue but
I found that queue member B doesn't
Thanks. I have checked that the queue.conf. I keep the default
setting as autofill=yes in my tests. That's mean even autofill=yes,
the 1st caller will still stick the whole queue.
asterisk version : 1.4.18
--queue.conf--
; AutoFill Behavior
;The old/current behavior of the queue has a
Rilawich Ango wrote:
Thanks. I have checked that the queue.conf. I keep the default
setting as autofill=yes in my tests. That's mean even autofill=yes,
the 1st caller will still stick the whole queue.
asterisk version : 1.4.18
--queue.conf--
; AutoFill Behavior
;The old/current
Hi,
I have set a queue 5000 with a agent logged in. When an user
dial 5000, will ring and then answer the call. Queue function
will execute and recording is started. However, the recorded wav file
is not a valid file with just a few bytes. Anyone can help me to
enable the recording
13 matches
Mail list logo
