It is threaded, but like the article said, there are some problems with how threads were used that limit call volume. I've run into that deadly 'avoiding deadlock' issue numerous times when handling 100+ simultaneous calls on an instance. The answer there was to run multiple instances of asterisk so that the calls could be balanced over multiple CPU's/cores
Containment of a call's resources has always bothered me in Asterisk, and likely comes back to this master thread again. I wish that something going wrong in one channel didn't take out all the others. For example, the voicemail application not terminating at the end of a call can still block any new calls, and needs a restart to get things back in order. On Tue, Apr 22, 2008 at 11:28 PM, Duane <[EMAIL PROTECTED]> wrote: > Jim Van Meggelen wrote: > > http://www.freeswitch.org/node/117 > > I do believe there was a discussion on asterisk being threaded here a > few weeks back :) > > -- > > Best regards, > Duane > > http://www.freeauth.org - Enterprise Two Factor Authentication > http://www.nodedb.com - Think globally, network locally > http://www.sydneywireless.com - Telecommunications Freedom > http://e164.org - Global Communication for the 21st Century > > "In the long run the pessimist may be proved right, > but the optimist has a better time on the trip." > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- | It ain't what you don't know that gets you into trouble. It's what | you know for sure that just ain't so. -- Mark Twain | | The Toronto Asterisk Users Group | Join the discussion group by visiting http://taug.ca --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
