[Asterisk-Dev] Question/Future Request for Call Queues

Chris A. Icide chris at netgeeks.net
Tue Sep 21 15:26:17 MST 2004


On 05:58 AM 9/21/2004, Paul van Brouwershaven wrote:
 >Hi,
 >
 >System information:
 >- Fedora Core 1
 >- Kernel 2.4.22-1.2115.nptl
 >- Asterisk CVS-HEAD-09/08/04-17:43:15
 >
 >1.> If a user is in the que and the expected wait time is longer then xxx
 >seconds or there are more then xxx callers. Play a sound from directory
 >xxx (advertisement)
 >
 >2.> Specify a member sequence, you can currently specify an agument like:
 >
 >member => SIP/user,1 (ringing with first attempt)
 >member => SIP/someuser,2 (ringing with first attempt)
 >member => SIP/otheruser,3 (ringing with first attempt)
 >member => SIP/someotheruser,3 (ringing with first attempt)
 >
 >But this sequence is not working as I aspected. I aspected that it's
 >working like:
 >
 >member => SIP/user,1 (ringing with first attempt)
 >member => SIP/someuser,2 (ringing with second attempt)
 >member => SIP/otheruser,3 (ringing with third attempt)
 >member => SIP/someotheruser,3 (ringing with third attempt)
 >

Also, if a queue has active agents, and there are no calls waiting in a 
queue, then a new queue call should immediately create an agent poll event 
instead of first playing the queue positions, hold time(if applicable), and 
thankyou messages.

Also another item of note:  If you have a queue with agents with multiple 
priorities, and an agent is off hook busy (as in the agent is placing a 
call - and used AgentCallBackLogin to logon) the system will try and ring 
that agent's priorty in the queue for what seems about 8 seconds before 
moving on to the next priority.  In the case where you have multiple 
priorities, you could hang a caller out to dry for a good 30 seconds before 
ringing an agent that was available when the call first came in.




More information about the asterisk-dev mailing list