[asterisk-users] Short rings for extensions when part of the Queue

[Bruce B]

Chad,

You are absolutely right on this one. I had setup the Queue time out for
agent set to 15 seconds and retry to 2 seconds. So, I think during those two
seconds Asterisk for some crazy reason hits another extension and then comes
back to the same extension to ring again. So, I have setup the agents to
ring for ever for this call center since their agents always have to present
or logout if not present. I will see the behavior tomorrow as they test it.

My issue might be solved but for those call centers where you want the Queue
to move onto the next agent or if you don't want to ring for ever and take a
Retry break then it will still remain an issue. I will report back if
setting to ring Unlimited doesn't work.

Warren,
The CLI shows the regular stuff. Nothing out of the ordinary but that it
move on to the next agent because the first agent has timed-out for two
seconds.

Regards,
Bruce

On Thu, Nov 4, 2010 at 9:29 PM, Chad Wallace <cwallace at lodgingcompany.com>wrote:

> On Thu, 4 Nov 2010 20:12:54 -0400
> Bruce B <bruceb444 at gmail.com> wrote:
>
> > Hi Everyone,
> >
> > We have three different Queues set to "leastrecent" strategy and from
> > time to time I hear someone complain that they receive short rings
> > (partial ring cycle) and since it's not their turn even if they
> > pickup the phone the call is not given to them since the Queue is
> > actually hitting someone else at the same time.
> >
> > Is this short ring an indication of some sort for "leastrecent"
> > strategy. Like maybe you are next in turn or something?
> >
> > It's annoying and odd that I don't see a pattern to it. If it's a
> > feature please let me know.
> >
> > Using Asterisk 1.4x
>
> We have the same issue, and I think I've figured out what's causing it,
> by watching the SIP debug output.
>
> What I noticed is that when someone misses a call on the queue, it
> switches over to the next person, but almost immediately (after a short
> ring) it breaks off and cancels that call because of a timeout.  I
> think it's a matter of timing between the different timeouts you can
> set in queues.conf.  I haven't had time to tweak it yet, so that's all
> I can tell you.  I don't know how hard it would be to get the timeouts
> to jive perfectly, but I'm sure it can be done.
>
> Mind you, this is based on only one observation, so I may be
> wrong...  It's only a minor annoyance, and I have bigger fish to fry
> right now.  Speaking of which, one of them is almost burnt, so I have
> to go. ;-)
>
> I'd be interested to hear your findings...
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20101105/daebf97b/attachment.htm