| Summary: | ASTERISK-05656: Major problem with queues in 1.2.0 | ||
| Reporter: | Manvir Randhawa (bulldozer) | Labels: | |
| Date Opened: | 2005-11-20 12:28:57.000-0600 | Date Closed: | 2011-06-07 14:11:57 |
| Priority: | Trivial | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I just upgraded my Asterisk Box from 1.0.9 to 1.2. In 1.0.9 queues were functioning perfectly however on upgrading to 1.2 the call queues went for a 6. I am facing the following problems- 1. If i have 3 extentions(100,102,103) logged into queue as agents and i try to call the queue from extention 104, the first extention(100) starts ringing. If 100 doesnot answer the call, the call is dropped and not transferred to the other two extention. However if 100 is busy, 102 starts ringing. And here if 102 doesn't answer the call, the call is dropped. 2. If all three agents are busy, and a call comes in queue, it is dropped after 15 seconds (This is the timeout for agents). My Queues configuration is following [201] wrapuptime=0 timeout=23 strategy=roundrobin retry=5 queue-youarenext=queue-youarenext queue-thereare=queue-thereare queue-thankyou=queue-thankyou queue-callswaiting=queue-callswaiting music=default monitor-join=yes monitor-format= member=Local/105@from-internal maxlen=0 leavewhenempty=no joinempty=yes context= announce-holdtime=yes announce-frequency=15 --------------------------- I tried a workarround to the above issue that worked but other problems started pouring in. The work arround - ------------------- okay i have solved the above problem by giving the same queue as a failover destinaiton. It works fine but now I have a different problems- The new problems- ------------------ 1 If all 3 agents are busy and a 2 calls come in queue (that makes it a total of 5 calls - 3 in progress and 2 in queue). The 2 calls that are in queue remain in queue forever even if all 3 agents get free. 2. My second problem is - if all three agents are busy, and one call comes in queue, the caller in queue hears onhold music but no caller queue position announcement. However while this caller(123) is still in queue and another caller (124) calls into the queue, both the callers (123 and 124) start hearing the caller queue position but caller that called later (124) hears that he is no 1 in queue and the caller that called earlier(123) hears that he is 2nd in queue. And both these callers remain in queue for ever even after all three agents get free. 3. The third problem is that the caller hears Position announcement every 2 seconds even when the frequency is set to 15 seconds. I think this is a major bug with queues. Cheers Manvir | ||
| Comments: | By: BJ Weschke (bweschke) 2005-11-20 16:35:03.000-0600 what does your agents.conf look like, minus passwords? By: Manvir Randhawa (bulldozer) 2005-11-20 19:41:34.000-0600 There is nothing in agents.conf file. I created this queue through AMP. A queue created in the exact way worked perfectly fine in Asterisk 1.0.9. The agents though are extentions 100, 102, 103. They log into the queue by dialing 201*. The extentions that call into the queue are - 120, 121, 122, 123, 124. The point is if 120 dials the queue number, 100 starts ringing and if 100 doesn't respont, instead of 102 ringing, the call is dropped. I am using round robin scheduling. This scenario would work perfectly well in Asterisk 1.0.9 but doens't work at all in 1.2.0. Is there any way I can use 1.0.9 app_queue in 1.2.0? By: Manvir Randhawa (bulldozer) 2005-11-20 20:54:58.000-0600 Okay one issue resolved. At least the call is not being dropped now. It seems Queues in 1.2.0 do not take 0 as a timeout argument for an indefinate timeout. I changed it to 1000 most of the problems solved. Let me test it thoroughly and then i'll write me comments again. :) By: Manvir Randhawa (bulldozer) 2005-11-21 01:34:55.000-0600 Okay my total problem solved. It is a minor bug that has had me up for the past 5 nights. It seems Queues in 1.2.0 do not take 0 as a timeout argument for an indefinate timeout. I changed the timeout to a positive integer and bingo everything falls in place. Im happy and jumping. Cheers Manvir By: BJ Weschke (bweschke) 2005-11-21 07:46:26.000-0600 closed per user request | ||