In both queues have the same wrapuptime, thereīs not a problem...<br>With weight property I canīt resolve my problem...I want to answer calls of both queues sorted by time, like a big FIFO or like if I had only one queue<br>
<br>regards<br><br><br><div class="gmail_quote">On Fri, Nov 28, 2008 at 12:31 PM, Atis Lezdins <span dir="ltr"><<a href="mailto:atis@iq-labs.net">atis@iq-labs.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, Nov 28, 2008 at 4:16 PM, Darrin Henshaw <<a href="mailto:DHenshaw@ignition.bm">DHenshaw@ignition.bm</a>> wrote:<br>
> One thing you also will run into is listed here:<br>
> <a href="http://www.voip-info.org/wiki/view/Asterisk+config+queues.conf" target="_blank">http://www.voip-info.org/wiki/view/Asterisk+config+queues.conf</a>.<br>
><br>
><br>
><br>
> Here is the interesting part:<br>
><br>
><br>
><br>
> Note that calls are not offered to queue members whilst the announcement is<br>
> playing and it is possible for callers to slip ahead in the queue as a<br>
> result. For example, call 1 arrives and is queued. Call 2 arrives ten<br>
> seconds later and is queued. After twenty seconds, call 1 is played the<br>
> periodic announce message. Exactly one second after call 1 starts hearing<br>
> the message an agent becomes free. Since call 1 is tied up with<br>
> announcements, call 2 is successfully offered to the agent. Call 1 remains<br>
> on hold and yet a call which arrived later has been serviced.<br>
><br>
><br>
><br>
> Basically you can see that if you have announcements played, that could<br>
> cause your order of answered calls to be not what you expect.<br>
<br>
</div>With queues there are much more such situation than just this one ;)<br>
<div class="Ih2E3d"><br>
><br>
><br>
><br>
> Cheers,<br>
><br>
><br>
><br>
> Darrin Henshaw | IT Administrator | MCTS: Exchange 2007 | MCSE 2003 | LPIC<br>
><br>
> Ignition Support Center | <a href="http://www.ignition.bm" target="_blank">www.ignition.bm</a><br>
><br>
> Bermuda (441) 496-4319 | Cayman (345) 947-4357 | Halifax (902) 482-1288<br>
> Atlanta | Bermuda | Cayman | Halifax<br>
><br>
><br>
><br>
> From: <a href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a><br>
> [mailto:<a href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>] On Behalf Of equis software<br>
> Sent: Friday, November 28, 2008 10:06<br>
> To: Asterisk Users Mailing List - Non-Commercial Discussion<br>
> Subject: Re: [asterisk-users] Priority between calls from different queues<br>
><br>
><br>
><br>
> I saw QUEUE_PRIO but it works inside a queue not between queues.<br>
><br>
> I need to use two queues because their have different settings like max time<br>
> waiting, max amount of calls in queue and others.<br>
<br>
</div>For in-between queues you can use weight. So, if queue1 has more<br>
weight than queue2, and agent1 is available (and is in both queues),<br>
he will receive call from queue1 (no matter how long other caller<br>
waits in queue2).<br>
<br>
Also, there's wrapuptime. It means - how many seconds agent should not<br>
receive call after completing previous queue call. So, if agent<br>
receives call from queue1 and it has wrapuptime 10 seconds, then he<br>
ends call, he might immediately receive call from queue2 - no matter<br>
that queue2 has lower weight or whatever settings. To overcome this,<br>
you have to enable shared_lastcall (available since 1.6.0).<br>
<br>
Regards,<br>
<font color="#888888">Atis<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
><br>
> Regards<br>
><br>
> On Fri, Nov 28, 2008 at 11:34 AM, Atis Lezdins <<a href="mailto:atis@iq-labs.net">atis@iq-labs.net</a>> wrote:<br>
><br>
> On Fri, Nov 28, 2008 at 1:13 PM, equis software <<a href="mailto:equissoftware@gmail.com">equissoftware@gmail.com</a>><br>
> wrote:<br>
>> Hi!<br>
>> I want to know the way that calls are answer in this case...<br>
>> I have queue1 and queue2, one agent that receive call from both queues.<br>
>><br>
>> queue1 <- call1<br>
>> queue1 <- call2<br>
>> queue2 <- call3<br>
>> queue2 <- call4<br>
>><br>
>> In my test the agent answer calls in this order: call1,call3,call2 and<br>
>> call4.<br>
>> I think this must be in this order call1,call2, call3, call4 like a big<br>
>> FIFO.<br>
>><br>
>> Its ok this behavior?<br>
>> Could I set priority between queues?<br>
>><br>
><br>
> Hello,<br>
><br>
> Queue has lot of different settings, like wrapuptime, strategy, etc.<br>
> Also two queues usually don't know about each other, with few<br>
> exceptions. One of them is shared_lastcall (introduced in Asterisk<br>
> 1.6.0). There's also weight - it will help to give priority to<br>
> specific queue if multiple calls are ready to go to agent in different<br>
> queues. Also, you can give priority to different callers within queue<br>
> by setting QUEUE_PRIO variable before sending call to queue.<br>
><br>
> You could try to describe why you need two queues and what should be<br>
> rules to distribute calls - so we can help you with overall<br>
> architecture.<br>
><br>
> Regards,<br>
> Atis<br>
><br>
><br>
><br>
><br>
><br>
> --<br>
> Atis Lezdins,<br>
> VoIP Project Manager / Developer,<br>
> IQ Labs Inc,<br>
> <a href="mailto:atis@iq-labs.net">atis@iq-labs.net</a><br>
> Skype: atis.lezdins<br>
> Cell Phone: +371 28806004<br>
> Cell Phone: +1 800 7300689<br>
> Work phone: +1 800 7502835<br>
><br>
> _______________________________________________<br>
> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
><br>
> asterisk-users mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
><br>
><br>
><br>
> ________________________________<br>
> This email and its attachments may be confidential and are intended solely<br>
> for the use of the individual or parties' to whom it is addressed. All<br>
> comments are solely those of the author and do not necessarily represent<br>
> those of Ignition. If you are not the intended recipient of this email and<br>
> its attachments, you must take no action based upon them, nor must you copy<br>
> or show them to anyone. Please contact the sender if you believe you have<br>
> received this email in error. Thanks for considering the environmental<br>
> impact before printing this email.<br>
><br>
> _______________________________________________<br>
> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
><br>
> asterisk-users mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
><br>
<br>
<br>
<br>
</div></div>--<br>
<div><div></div><div class="Wj3C7c">Atis Lezdins,<br>
VoIP Project Manager / Developer,<br>
IQ Labs Inc,<br>
<a href="mailto:atis@iq-labs.net">atis@iq-labs.net</a><br>
Skype: atis.lezdins<br>
Cell Phone: +371 28806004<br>
Cell Phone: +1 800 7300689<br>
Work phone: +1 800 7502835<br>
<br>
_______________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br>