Instead of "call-limit=1" try o use "incominglimit=1".
Note that this is not a fix, but more a "workaround"... I guess the queue module still has allot of bugs... or it isn't sufficiently documented to be correctly used. -----Mensagem original----- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Em nome de Wes Baehr Enviada: segunda-feira, 3 de Abril de 2006 20:16 Para: 'Asterisk Users Mailing List - Non-Commercial Discussion' Assunto: [Asterisk-Users] Queues - Dumb question It was my understanding that when an agent answers a queue call, he will not be hit with another call until he finishes his current call. Currently, my agents get hit with calls from the queue while they are still on a previous call, so I've resorted to setting their "call-limit" in sip.conf to 1. But, this prevents them from putting one call on hold and making another call (although they could use parking). Maybe I misunderstood, but I'm asking anyway :) Running asterisk 1.2.4 Queue config: [staff] musiconhold = classical context=queue-staff announce = beep strategy = ringall context = queue-staff timeout = 20 retry = 10 wrapuptime = 20 announce-frequency = 120 timeoutrestart = yes eventwhencalled = yes joinempty=strict leavewhenempty=yes reportholdtime=yes _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users