I don't see why I'd be getting CHANUNAVAIL. As I said, all the agents are logged in and are in astdb and 'sip show peers'. I just had another go, I passed a timeout of 300 to the Queue() command and set timeout=30 in queues.conf for the queue. The Queue timed out after TWO minutes (120s) and only rang 4 of the 6 agents (30s each). It also then did not continue execution at the next priority in the dial plan. I also tried with a timeout of 300 passed to Queue() but a timeout of 15 in queues.conf. It rang ALL 6 agents for 15s each. This is well below the queue timeout of 300s, but at this point it stopped, and didn't continue at the next priority in the dialplan. See what I mean? If I go and change some timeouts around, the behaviour becomes equally screwy, but for a different reason. Yeah I saw that link earlier today.... based on the results I'm getting it isn't much help, Doug.
-----Original Message-----
From: CC Jay [mailto:[EMAIL PROTECTED]
Sent: Thu 3/23/2006 10:32 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Cc:
Subject: Re: [Asterisk-Users] Tearing my hair out with Queues
"300" is the maximum time a call can be placed in a queue, after that,
next priority will be executed.
"15" is the time each agent will be rung before * tries the next agent.
"CHANUNAVAIL" happens since Queue rings Agent/xyz, Agent/xyz in turn
tries to ring SIP/abc but cannot find it, hence...
BTW, you may find this helpful:
http://www.oinko.net/astrecipes/index.php?n=118
Cheers
<<winmail.dat>>
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
