asterisk users - Jun 2010 - Using Local in queues a good idea? (or at least not a very bad idea?)

Hi,

I'm now thinking of always dialing out to Local/xxx at outbound/n on all my
queue members.
The reason for this, is both to be able to limit the number of calls to one
agent, and to have fail-over-lines on the agents.
(for example, if dahdi fails, go sip)

But for a few years ago, I did some testing with Local/ channels, and they
seemed somewhat unstable in large quantity.

Are they more safe now? Is it safe to use local channels with the /n
modifier as queue members? (i need the n modifier to be able to count
continous calls using the h extension).
Lets say it would be around 200 Local channels at max with a lot of calls
ending and starting. And a lot of Local channels being created and removed
as call attempts in queues fail when either the destination line is busy, or
if the local channel context returns Busy() because of call limits.

Regards,
H?kon Nessj?en
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20100604/f3bfe904/attachment.htm

H?kon Nessj?en <haakon at avelia.no> writes:
> But for a few years ago, I did some testing with Local/ channels, and they
> seemed somewhat unstable in large quantity.
>
> Are they more safe now? Is it safe to use local channels with the /n
> modifier as queue members? (i need the n modifier to be able to count
> continous calls using the h extension).
They are pretty good in late 1.6.0.x at least.

There are some issues though. E.g. Queue sometimes has trouble
determining whether a given extension is busy or not, and therefore
sends calls to a busy extension. When you return Busy in your Local
channel and the queue is set to ringall, Queue just sends the call right
back into the Local channel, causing load problems. Workaround: Detect
whether the call comes from a queue with ringall strategy and do a
Wait(1000) instead of returning Busy.


/Benny