<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
We run with ringall strategy, and have had shared_lastcall on for six
months. afaik, this only shares the last call data for things like
wrapup time; it definitely does not share how the queues with ringall
hand off their queued calls.<br>
<br>
As for the patch below, I have since tried it on 1.4.29, and it does
not apply cleanly due to the interface_state patch from digium added
from 1.6, as well as some other minor code changes. I have added a
patch for 1.4.29 to the same directory listed below. It compiles and
passes very basic testing, but has not been run in production.<br>
<br>
-Steve <br>
<br>
On 01/22/2010 07:53 AM, Lenz Emilitri wrote:
<blockquote
cite="mid:699ee941001220653m50d0864cs186337d99c43f701@mail.gmail.com"
type="cite">
<div>Maybe I'm saying something stupid, but I thought this was what
shared_lastcall would do with a leastrecent strategy.<br>
</div>
<div><br>
</div>
<div>; shared_lastcall will make the lastcall and calls received be
the same in<br>
; members logged in more than one queue.<br>
; This is useful to make the queue respect the wrapuptime of another
queue<br>
; for a shared member<br>
;<br>
shared_lastcall=no<br>
<br>
</div>
<div>I did not really try it, just read the docs.</div>
<div>l.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<br>
<div class="gmail_quote">2010/1/20 Steven Alligood <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:steve@bluehost.com">steve@bluehost.com</a>></span><br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">This
email is not a question, but a potential solution to any who have had
the same issue I have faced.<br>
<br>
If you have agents logged in to multiple queues at the same time,
Asterisk does not handle the answering of those queues in any set order
or sequence. It has no way of prioritizing calls in between the shared
queues, to guarantee that the queue with the call that has the longest
hold time will be answered next.<br>
<br>
If Asterisk is configured with several queues and all queues have calls
waiting, when an Agent becomes available, Asterisk randomly picks the
queue that will be answered next. This can be a problem adversely
affecting service levels since the queue with the call having the
longest hold time may be essentially ignored for several cycles of
available agents.<br>
<br>
To fix this issue, we had a custom patch written for the 1.4 branch.
Digium has decided to not include it in the 1.6 branch, so I am making
the 1.4 patch available for any who want or need it. It works well on
1.4.19.1, but I have not tried it on anything after that (I am
currently running 1.6 and have the issue back again).<br>
<br>
Questions are always welcome, though I may or may not have the answers,
as I am not the coder, just the asterisk admin.<br>
<br>
As always, if you need it/ want it in your production systems, it would
be good to send an email to Digium letting them know that.<br>
<br>
-Steve<br>
<br>
Patch at: <a moz-do-not-send="true"
href="http://mirrors.bluehost.com/asterisk" target="_blank">http://mirrors.bluehost.com/asterisk</a><br>
<br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="http://lists.digium.com/mailman/listinfo/asterisk-users"
target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Loway - home of QueueMetrics - <a moz-do-not-send="true"
href="http://queuemetrics.com">http://queuemetrics.com</a><br>
<br>
</blockquote>
</body>
</html>