Sounds like you don't have the device status updating the Local channel correctly. Make sure you're using a recent version of 1.4 (or any 1.6.x version) and use the device state option to the AddQueueMember() application so that you can assign a SIP device to watch for device status for instead of letting the Local channel magically make one up :)
(without it, the Local channel can sit in a busy or unavailable state even when the device is actually available) Leif Madsen. On Tue, Jul 21, 2009 at 2:45 PM, Andre Courchesne<[email protected]> wrote: > Anyone has an idea why a call would go blocking a queue. I only have the > following in the logs. Calls would pile-up behind this one but would never > get sent out to the waiting available agents. After i did a soft hangup on > that zap/31-1 channel, calls would flow correctly... > > [Jul 21 14:07:33] VERBOSE[1657] logger.c: -- Executing > [1...@ext-queues:9] Queue("Zap/31-1", "1000|tr||") in new stack > [Jul 21 14:07:39] VERBOSE[1657] logger.c: -- > Local/13...@from-internal-c941,1 is busy -- Leif Madsen. http://www.leifmadsen.com http://www.oreilly.com/catalog/asterisk --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
