What it actually does is tell the SIP channel driver to track whether or not any given peer has a call to it. It can then subsequently inform the Queue application so that another call will not be given to that user. If you did not have the ringinuse=no in your queue definition, you would then be able to receive up to 5 simultaneous calls (after five, then the SIP channel driver would return busy and Queue wouldn't be able to dial that peer). Regards, - Brad
________________________________ From: [EMAIL PROTECTED] on behalf of James Fromm Sent: Fri 1/19/2007 6:07 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Queue and Interface time out That worked. I don't understand what call-limit has to do with this. I set it to 5. Why does that keep the member interface from getting a second call from the Queue application? I would think it would allow the member interface to get up to 5 calls. The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
<<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
