Maybe I'm saying something stupid, but I thought this was what
shared_lastcall would do with a leastrecent strategy.
; shared_lastcall will make the lastcall and calls received be the same in
; members logged in more than one queue.
; This is useful to make the queue respect the wrapuptime of
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.
As for the patch below, I have since tried it on 1.4.29,
This email is not a question, but a potential solution to any who have
had the same issue I have faced.
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
