Thank you for that summary. It's some of the best independent documentation of an OSS product that I've ever seen, among the best code docs period (in 30 years of reading others' code). If Asterisk included such concise description of each step through scopes of the call graph for every use case, its use would explode (even more than it's exploding now), like Apache. I wish this were the default way to document the system, and all OSS.
On Tue, 2006-09-12 at 22:54 -0700, [EMAIL PROTECTED] wrote: > Date: Tue, 12 Sep 2006 16:34:53 -0500 > From: "Moises Silva" <[EMAIL PROTECTED]> > Subject: Re: [asterisk-dev] Learning Asterisk Internals > To: "Asterisk Developers Mailing List" <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > what's the best way to > > learn asterisk internals? > > Read the source code. > > 1. A SIP call usually starts in sipsock_read(), that is a callback > function executed when the SIP socket has stuff to be read. [...] > 11. The original channel will return to PBX extensions execution in > extensions.conf, ready to execute other commands such as Playback() or > even other Dial() > > Regards. > > - Moises Silva -- (C) Matthew Rubenstein _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-biz mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-biz
