similar to: roundrobin and rrmemory with pre-defined agent order

Dear all, I can't understand the diff between roundrobin and rrmemory strategy. Could you explain for me ? and is roundrobin means each available interface ring once or several times and ring another? ; A strategy may be specified. Valid strategies include: ; ; ringall - ring all available channels until one answers (default) ; roundrobin - take turns ringing each available interface ;

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

Hi, I made a simple menu using the Background application and some wav files. I converted the wav files using for a in *.wav; do sox "$a" -r 8000 -c1 "`echo $a|sed -e s/wav//`gsm"; done (from http://www.voip-info.org/wiki/index.php?page=Convert%20WAV%20audio%20files%20for%20use%20in%20Asterisk) The first two files "01/bemvindo" and "01/menu_top" are good.

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 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

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,

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

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

I've just started consulting for a SME client based in Reston Virginia. They don't know it yet but they are going to need a hosted asterisk service and some DID's. Email me if you are able to provide 10 DID's in Reston (must be able to be ported away!!) and hosted Asterisk with end user configurable IVR etc. Probably only 5-8 users at the moment BUT... they'll be

Hi, all. I'm checking in about an issue that has been mentioned here a few times, but to which I can't seem to find a solution for a very present need. The summary is that we'd like to have a queue that rings logged-in agents in the same order every time, based on penalty, in a way that continuously escalates the attempts to the next penalty level until all agents have been tried.

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 struggle to set up a simple round-robin queue, where I can determine the order in which the members are tried. My queues.conf is currently: [TechSupportQ] strategy = roundrobin context = techSupportQueued timeout = 10 retry = 1 wrapuptime=3 maxlen = 0 joinempty = yes member = SIP/405 member = SIP/403 member = SIP/402 I am not using Agents (defined in agents.conf), because I

I get congestion (same error) with exten => _NXXNXXXXXX,1,Dial(SIP/${EXTEN:1}@xxx.xxx.xxx,30,r) not dialing 1 exten => _1NXXNXXXXXX,1,Dial(SIP/${EXTEN:1}@xxx.xxx.xxx,30,r) dialing 1 exten => _91NXXNXXXXXX,1,Dial(SIP/${EXTEN:1}@xxx.xxx.xxx,30,r) dialing 9 All the same == Parsing '/etc/asterisk/sip_notify.conf': Found -- Executing [9544790554 at To_Airspring:1]

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

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

struct xfirstStru { int var1; double var2; int var3; char *var4; }; %FIRSTSTRU_PLUSPLUS_TOTVS. = type { i32, double, i32, i8* } Hi, I had not applied the layout at run time, only during the emission of the .bc. Now it's running ok when I allocate the structure point at LLVM side, but, when I allocate the structure pointer in the C

I'm happy to be able to announce the release of Xapian 1.2.19, which you can download from: http://xapian.org/download Since 1.2.16, release tarballs are compressed with xz instead of gzip, as it provides much better compression, without being too slow to decompress. (For now at least, Search::Xapian is still gzipped.) We decided not to provide multiple formats for the downloads. The size

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

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