On 3/17/08, Rajkumar S <[EMAIL PROTECTED]> wrote: > On Mon, Mar 17, 2008 at 6:30 PM, Grygoriy Dobrovolskyy > <[EMAIL PROTECTED]> wrote: > > Forgot to add: > > Multiple queues fo sip phone, it is normal that sometimes it is ringed, as > > reported busy for 1 queue and free for another. you limitited incoming call > > to max 1 ' incominglimit=1' so ;) > > > My understanding was that if a SIP phone is busy, either due to a call > from queue or a call from another sip phone or even making an out > bound call, the queue application would detect that and skip trying > that channel. > > Is this assumption wrong ?
If that would be queue, it would have different log entry. This seems, a result from Dial(SIP/2505,,). There are two different settings. You can increase call-limit (or incominglimit) in sip.conf - so devices will be able to take several simultenous calls. So, even if SIP device has one call (and call-limit is more than one), device state of SIP device will be "In Use", and that's where ringinuse parameter of Queue application comes in - if set to 0, Queue won't ring and you will see a bit different message. Hope that this explains architecture. As for current problem - i suspect that device state don't get updated correctly for Queue application, so Queue tries to dial device, and call-limit blocks it from doing so. There's a patch, currently in testing (issue 12127), it should fix this, however if you intend to keep incominglimit to 1, and don't use local channels - there's nothing to worry about. Regards, Atis -- Atis Lezdins, VoIP Project Manager / Developer, [EMAIL PROTECTED] Skype: atis.lezdins Cell Phone: +371 28806004 Cell Phone: +1 800 7300689 Work phone: +1 800 7502835 _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users