similar to: is roundrobin and rrmemory the same meaning?

Hi, I would like to implement a queue using a circular strategy, I mean, using roundrobin or rrmemory strategies. However, I am not able to define the order Asterisk will call the agents once a new call arrives in the queue. Seems that Asterisk will always define its order as the queues.conf file is read, and most of times this order is different from the one I want (for each queue in

First of all I would like to thank Mark for getting roundrobin to go roundrobin. Good job. Now we have some options here for leastrecent and fewestcalls strategy. It needs some work on the logic and Mark recommend that I ask the list and get some input before he makes any changes to it. fewestcalls from what I have seen would always ring the agent with the fewestcalls first then go into

I have setup several Calling Queues, each setup with RoundRobin strategy. When I call the queue, the first member/agent phone rings. Great! I call it again, the second member/agent rings?? I thought that was the RRMemory strategy, but it seems RoundRobin is also doing it. Anyone know what I can do to my queues, in order to force each call down the ordering of my members list? --------------

I have set up an operator queue for our receptionist. That way, if she takes a break or is out, by logging out of the queue, calls to the "Operator" can be handled by other agents. I have set strategy = roundrobin in queues.conf. According to "the book" ATFoT, roundrobin always starts with the first agent in the queue. This is the desired result. I want all calls to start

Dear All, I've got a working asterisk installation which I need minor help from. Currently, I'm running a Sales Queue, which is answered by a selected group of people. Here are my queues.conf [sales-hotline] strategy = roundrobin timeout = 10 member = SIP/602 member = SIP/603 member = SIP/701 member = SIP/604 After calls come in, it works fine, however, I notice that even when SIP/602

I have a queue setup to 'roundrobin' (NOT roundrobin with memory). I have three agents. We'll call them 101, 102, and 103. When a call comes in.. I want it to always try 101 if no answer try 102.. if no answer try 103, etc. However, what it is doing is... it will ring 101... if 101 answers, next time a call comes in it will go to 102. This isn't at all what I want. Any ideas

Hi, I have the same problem with the queue configuration When I receive 2 calls only 1 phone ring even if more agent's phone are free. The second call will go to an other agent only if the first call is pickup. Somebody have a solution ? This is my config file : Queue.conf [general] ; ; Global settings for call queues ; ; Persistent Members ; Store each dynamic agent in each queue

Hey guys, i'm wondering if there is any good way to get app_queue working in real roundrobin strategy. The idea is to specify a call list of, lets say, 3 agants. Those agents should always be called in the correct defined order. So all calls have to get the following agent priority: 1st Agent -> 2nd Agent -> 3rd Agent I've actually solved that by defining penelty for the accounts,

Howdy, have working realtime queues using queue_members looking something like; queuea|Local/101@context|0 queuea|Local/102@context|1 queuea|Local/103@context|10 Regardless of what strategy is used in the queues (roundrobin,rrmemory,ringall etc) it wont escalate on NOANSWER Asterisk SVN-branch-1.2-r33841 Any clues are appreciated! /Danny

Seeing as the "leastrecent" strategy does not work for us (it will *always* call the leastrecent agent, even if that agent is busy, and will not move to the next agent) I thought I'd try the roundrobin strategy. This seemed to work - however, I had my supervisor telling me today that a certain agent seemed to be getting most of the calls - and when I checked, out of 50 inbound

Hi there, this is my queues.conf, I'm using todays CVS: [599] joinempty = yes musiconhold = default strategy = roundrobin servicelevel = 60 wrapuptime = 0 maxlen = 0 timeout=15 announce-frequency = 15 member => SIP/381 member => SIP/300 At first call 381 rings, if you hang up and call again you get the 300 ringing ... this looks more rrmemory than roundrobin, there is something wrong

It looks like this issue has been raised before, but I see it mostly ignored and no answers given, so here it is again: For the past couple of years, I've wanted a queue that works very similarly to roundrobin/rrmemory, but that doesn't remember anything about where the last ring went to. This new strategy would always start at the first member (as defined in queues.conf) when a new

Just woundering if the intentend functionality of leastrecent and fewestcalls it to continually dial only the first chosen ext. in the queue. In other words if a memeber is logged into the queue but doesn't answer the call the call never moves on in my configuration from that ext. This could be really bad!!!! Thanks [support] announce-frequency=45 strategy=leastrecent music=default

Hello list, I have been researching a bit into the way the queue app works and how different timeouts play together, and have prepared a short tutorial on understanding queue timeouts - see http://www.oinko.net/astrecipes/index.php?n=118 - any suggestion, error found or correction is welcome. While I was at it, I came across a strange bug: imageine you have three callback agents

Hi all, I have a need where ACD ringall and ACD roundrobin ring strategies will be combined. Basically, ring every agent in a specified order, but whenever it times out and goes to the next agent, I still need the previous agent(s) to continue to ring. I would like to develop this extension myself as a contribution to the asterisk community. In doing this, where should I start? I've

Hi, I'm trying to use Round Robin Memory with my queues. It seems to work fine... that being I call in.. first time agent 1 will get a call, second time agent 2, and so on. However, it seems if a period of time has gone by since agent 1 got a call (I don't know how much but say 10 minutes or so) when another call comes in.. agent 1 gets the call again. Can anyone confirm this? Is

We're moving a somewhat complicated call center over to an Asterisk system, and I'm looking for documentation on queue/agent configuration. So far I haven't found anything on the Digium or Asterisk websites, and I was hoping that someone could point me in the right direction. Thanks, Devon

Hi, I have configured a call queue as follows: [sales] music = default strategy = roundrobin timeout = 20 retry = 5 reportholdtime = yes announce = queue-sales member => Agent/9021 member => Agent/5901 member => Agent/9020 member => Agent/1114 Now, I would expect all calls to this queue to be delivered first to 9021, then to 5901, then to 9020, then to 1114 (all agents are logged in

Egads. Getting queues to work is like pulling teeth. extensions.conf: exten => q_main,1,Queue(oneeighty_main||||1) exten => 80014055,1,Dial(SIP/80014018,15,tr) exten => 80014057,1,Dial(SIP/80014018,15,tr) exten => 80014052,1,Dial(SIP/80014018,15,tr) queues.conf: [oneeighty_main] musiconhold = default joinempty = strict leavewhenempty = strict strategy = rrmemory retry = 0 member

Hello, I have Elastix ISO install (FreePBX 2.7.0.3) My current Setup is as follows: Inbound Route > Queue > (Dynamic Agents) The queue distributes calls based on rrMemory. I have been asked to redesign the call distribution as follows: Calls will be delievered to Level-1 Agents (say 4 dynamic agents) in rrMemory format. When Level-1 Agents are busy, distribute calls to Level-2 Agents