<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>query</TITLE>
</HEAD>
<BODY>
<BR>
<P><FONT SIZE=2>Hi ,</FONT>
</P>
<P><FONT SIZE=2>I am a new user to the asterix environment. </FONT>
<BR><FONT SIZE=2>We plan to build a telephony interface starting with the Digium's TDM31B and E100P. </FONT>
<BR><FONT SIZE=2>I would like to know how we can start off with the cards and later build our own drivers for the cards. Also we would like to extract the clock from the E1 line. Is it possible to do that and how? </FONT></P>
<BR>
<P><FONT SIZE=2>Thanks in advance</FONT>
</P>
<P><FONT SIZE=2>Regards</FONT>
<BR><FONT SIZE=2>Saurabh</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: asterisk-dev-request@lists.digium.com</FONT>
<BR><FONT SIZE=2>[<A HREF="mailto:asterisk-dev-request@lists.digium.com">mailto:asterisk-dev-request@lists.digium.com</A>]</FONT>
<BR><FONT SIZE=2>Sent: Wednesday, August 04, 2004 1:00 AM</FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Subject: Asterisk-Dev digest, Vol 1 #815 - 13 msgs</FONT>
</P>
<BR>
<P><FONT SIZE=2>Send Asterisk-Dev mailing list submissions to</FONT>
<BR> <FONT SIZE=2>asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>To subscribe or unsubscribe via the World Wide Web, visit</FONT>
<BR> <FONT SIZE=2><A HREF="http://lists.digium.com/mailman/listinfo/asterisk-dev" TARGET="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</A></FONT>
<BR><FONT SIZE=2>or, via email, send a message with subject or body 'help' to</FONT>
<BR> <FONT SIZE=2>asterisk-dev-request@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>You can reach the person managing the list at</FONT>
<BR> <FONT SIZE=2>asterisk-dev-admin@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>When replying, please edit your Subject line so it is more specific</FONT>
<BR><FONT SIZE=2>than "Re: Contents of Asterisk-Dev digest..."</FONT>
</P>
<BR>
<P><FONT SIZE=2>Today's Topics:</FONT>
</P>
<P><FONT SIZE=2> 1. RE: MYSQL application (Constantine Filin)</FONT>
<BR><FONT SIZE=2> 2. RE: RE: MYSQL application (Kevin Walsh)</FONT>
<BR><FONT SIZE=2> 3. Re: RE: MYSQL application (John Turner)</FONT>
<BR><FONT SIZE=2> 4. Re: RE: MYSQL application (Steven Critchfield)</FONT>
<BR><FONT SIZE=2> 5. RE: RE: MYSQL application (Domjan Attila)</FONT>
<BR><FONT SIZE=2> 6. Re: RE: MYSQL application (Andrew Kohlsmith)</FONT>
<BR><FONT SIZE=2> 7. Re: RE: MYSQL application (Steven Critchfield)</FONT>
<BR><FONT SIZE=2> 8. Re: RE: MYSQL application (Andrew Kohlsmith)</FONT>
<BR><FONT SIZE=2> 9. Re: RE: MYSQL application (Steven Critchfield)</FONT>
<BR><FONT SIZE=2> 10. Re: RE: MYSQL application (Domjan Attila)</FONT>
<BR><FONT SIZE=2> 11. minumum linux hardware-less than 100 mb (Serkan Albayrak)</FONT>
<BR><FONT SIZE=2> 12. Re: minumum linux hardware-less than 100 mb (Andrew Kohlsmith)</FONT>
<BR><FONT SIZE=2> 13. Re: minumum linux hardware-less than 100 mb (Miroslav Nachev)</FONT>
</P>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 1</FONT>
<BR><FONT SIZE=2>Date: Mon, 2 Aug 2004 18:34:57 -0700</FONT>
<BR><FONT SIZE=2>From: "Constantine Filin" <cfilin@intermedia.net></FONT>
<BR><FONT SIZE=2>To: <asterisk-dev@lists.digium.com></FONT>
<BR><FONT SIZE=2>Subject: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>Greetings=20</FONT>
</P>
<P><FONT SIZE=2>> While I understand the concern of too many 'vendor' specific</FONT>
<BR><FONT SIZE=2>> implementations, I applaud the inclusion of 'query', 'insert', etc.</FONT>
<BR><FONT SIZE=2>> commands into the asterisk dialplan versus through an AGI. If the</FONT>
<BR><FONT SIZE=2>general</FONT>
<BR><FONT SIZE=2>> consensus is to move this into ast_data, then that is good as well, as</FONT>
<BR><FONT SIZE=2>> long as the more useful database functions are not lost in the</FONT>
<BR><FONT SIZE=2>process.</FONT>
</P>
<P><FONT SIZE=2>There is no problem if MYSQL is not included in CVS, still I thought if</FONT>
<BR><FONT SIZE=2>this</FONT>
<BR><FONT SIZE=2>work well for me, then it might work for someone else as well.</FONT>
</P>
<P><FONT SIZE=2>On the subject of developing a single interface to all database from *</FONT>
<BR><FONT SIZE=2>dialplans - what about unix ODBC and commands like=20</FONT>
<BR> <FONT SIZE=2>ODBC(Connect DSN connID ...)</FONT>
<BR> <FONT SIZE=2>ODBC(Query ${connID} resultID ...)</FONT>
<BR> <FONT SIZE=2>ODBC(Fetch ${resultID} fetchID...)</FONT>
<BR> <FONT SIZE=2>ODBC(Disconnect ${connID} ...)</FONT>
<BR> <FONT SIZE=2>ODBC(Clear${resultID}</FONT>
<BR><FONT SIZE=2>would they be generic enough?</FONT>
</P>
<P><FONT SIZE=2>Thanks</FONT>
</P>
<P><FONT SIZE=2>Constantine</FONT>
</P>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 2</FONT>
<BR><FONT SIZE=2>From: "Kevin Walsh" <kevin@cursor.biz></FONT>
<BR><FONT SIZE=2>To: <asterisk-dev@lists.digium.com></FONT>
<BR><FONT SIZE=2>Subject: RE: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>Date: Tue, 3 Aug 2004 02:46:11 +0100</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>Constantine Filin [cfilin@intermedia.net] wrote:</FONT>
<BR><FONT SIZE=2>> > While I understand the concern of too many 'vendor' specific</FONT>
<BR><FONT SIZE=2>> > implementations, I applaud the inclusion of 'query', 'insert', etc.</FONT>
<BR><FONT SIZE=2>> > commands into the asterisk dialplan versus through an AGI. If the</FONT>
<BR><FONT SIZE=2>> > general consensus is to move this into ast_data, then that is good as</FONT>
<BR><FONT SIZE=2>> > well, as long as the more useful database functions are not lost in the</FONT>
<BR><FONT SIZE=2>> > process. </FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> There is no problem if MYSQL is not included in CVS, still I thought if</FONT>
<BR><FONT SIZE=2>> this work well for me, then it might work for someone else as well.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> On the subject of developing a single interface to all database from *</FONT>
<BR><FONT SIZE=2>> dialplans - what about unix ODBC and commands like</FONT>
<BR><FONT SIZE=2>> ODBC(Connect DSN connID ...)</FONT>
<BR><FONT SIZE=2>> ODBC(Query ${connID} resultID ...)</FONT>
<BR><FONT SIZE=2>> ODBC(Fetch ${resultID} fetchID...)</FONT>
<BR><FONT SIZE=2>> ODBC(Disconnect ${connID} ...)</FONT>
<BR><FONT SIZE=2>> ODBC(Clear${resultID}</FONT>
<BR><FONT SIZE=2>> would they be generic enough?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>ODBC is horribly inefficient. I wouldn't go near it. Perhaps a</FONT>
<BR><FONT SIZE=2>more generic interface would be better. Something like the</FONT>
<BR><FONT SIZE=2>following:</FONT>
</P>
<P><FONT SIZE=2> SQL(ODBC, Connect, ...)</FONT>
<BR><FONT SIZE=2> SQL(MySQL, Query, ...)</FONT>
</P>
<P><FONT SIZE=2>The various "database drivers" could be implemented as loadable</FONT>
<BR><FONT SIZE=2>modules, much like the codecs and applications etc.</FONT>
</P>
<P><FONT SIZE=2>Of course, that wouldn't be very much different from MySQL(...),</FONT>
<BR><FONT SIZE=2>but at least it wouldn't complicate the dialplan with an extra</FONT>
<BR><FONT SIZE=2>command for every database vendor.</FONT>
</P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2> _/ _/ _/_/_/_/ _/ _/ _/_/_/ _/ _/</FONT>
<BR><FONT SIZE=2> _/_/_/ _/_/ _/ _/ _/ _/_/ _/ K e v i n W a l s h</FONT>
<BR><FONT SIZE=2> _/ _/ _/ _/ _/ _/ _/ _/_/ kevin@cursor.biz</FONT>
<BR><FONT SIZE=2>_/ _/ _/_/_/_/ _/ _/_/_/ _/ _/</FONT>
</P>
<BR>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 3</FONT>
<BR><FONT SIZE=2>From: John Turner <jdturner@nc.rr.com></FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>Date: Mon, 2 Aug 2004 23:22:49 -0400</FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>On Aug 2, 2004, at 9:46 PM, Kevin Walsh wrote:</FONT>
</P>
<P><FONT SIZE=2>> Constantine Filin [cfilin@intermedia.net] wrote:</FONT>
<BR><FONT SIZE=2>>>> While I understand the concern of too many 'vendor' specific</FONT>
<BR><FONT SIZE=2>>>> implementations, I applaud the inclusion of 'query', 'insert', etc.</FONT>
<BR><FONT SIZE=2>>>> commands into the asterisk dialplan versus through an AGI. If the</FONT>
<BR><FONT SIZE=2>>>> general consensus is to move this into ast_data, then that is good as</FONT>
<BR><FONT SIZE=2>>>> well, as long as the more useful database functions are not lost in </FONT>
<BR><FONT SIZE=2>>>> the</FONT>
<BR><FONT SIZE=2>>>> process.</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>> There is no problem if MYSQL is not included in CVS, still I thought </FONT>
<BR><FONT SIZE=2>>> if</FONT>
<BR><FONT SIZE=2>>> this work well for me, then it might work for someone else as well.</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>> On the subject of developing a single interface to all database from *</FONT>
<BR><FONT SIZE=2>>> dialplans - what about unix ODBC and commands like</FONT>
<BR><FONT SIZE=2>>> ODBC(Connect DSN connID ...)</FONT>
<BR><FONT SIZE=2>>> ODBC(Query ${connID} resultID ...)</FONT>
<BR><FONT SIZE=2>>> ODBC(Fetch ${resultID} fetchID...)</FONT>
<BR><FONT SIZE=2>>> ODBC(Disconnect ${connID} ...)</FONT>
<BR><FONT SIZE=2>>> ODBC(Clear${resultID}</FONT>
<BR><FONT SIZE=2>>> would they be generic enough?</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>> ODBC is horribly inefficient. I wouldn't go near it. Perhaps a</FONT>
<BR><FONT SIZE=2>> more generic interface would be better. Something like the</FONT>
<BR><FONT SIZE=2>> following:</FONT>
<BR><FONT SIZE=2>></FONT>
</P>
<P><FONT SIZE=2>Why not something like Perl DBI? Here is a C library that could be </FONT>
<BR><FONT SIZE=2>used as the backend.</FONT>
</P>
<P><FONT SIZE=2><A HREF="http://libdbi.sourceforge.net/" TARGET="_blank">http://libdbi.sourceforge.net/</A></FONT>
</P>
<P><FONT SIZE=2>John</FONT>
</P>
<BR>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 4</FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>From: Steven Critchfield <critch@basesys.com></FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Date: Mon, 02 Aug 2004 22:33:26 -0500</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>On Mon, 2004-08-02 at 22:22, John Turner wrote:</FONT>
<BR><FONT SIZE=2>> On Aug 2, 2004, at 9:46 PM, Kevin Walsh wrote:</FONT>
<BR><FONT SIZE=2>> > ODBC is horribly inefficient. I wouldn't go near it. Perhaps a</FONT>
<BR><FONT SIZE=2>> > more generic interface would be better. Something like the</FONT>
<BR><FONT SIZE=2>> > following:</FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Why not something like Perl DBI? Here is a C library that could be </FONT>
<BR><FONT SIZE=2>> used as the backend.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> <A HREF="http://libdbi.sourceforge.net/" TARGET="_blank">http://libdbi.sourceforge.net/</A></FONT>
</P>
<P><FONT SIZE=2>Check the licensing and then follow any thread about licensing</FONT>
<BR><FONT SIZE=2>requirements and copyright for asterisk. Then you will know why we can't</FONT>
<BR><FONT SIZE=2>use it.</FONT>
<BR><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Steven Critchfield <critch@basesys.com></FONT>
</P>
<BR>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 5</FONT>
<BR><FONT SIZE=2>Subject: RE: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>From: Domjan Attila <adomjan@tvnet.hu></FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Date: Tue, 03 Aug 2004 10:14:49 +0200</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>On Tue, 2004-08-03 at 03:46, Kevin Walsh wrote:</FONT>
<BR><FONT SIZE=2>> Constantine Filin [cfilin@intermedia.net] wrote:</FONT>
<BR><FONT SIZE=2>> > > While I understand the concern of too many 'vendor' specific</FONT>
<BR><FONT SIZE=2>> > > implementations, I applaud the inclusion of 'query', 'insert', etc.</FONT>
<BR><FONT SIZE=2>> > > commands into the asterisk dialplan versus through an AGI. If the</FONT>
<BR><FONT SIZE=2>> > > general consensus is to move this into ast_data, then that is good as</FONT>
<BR><FONT SIZE=2>> > > well, as long as the more useful database functions are not lost in the</FONT>
<BR><FONT SIZE=2>> > > process. </FONT>
<BR><FONT SIZE=2>> > ></FONT>
<BR><FONT SIZE=2>> > There is no problem if MYSQL is not included in CVS, still I thought if</FONT>
<BR><FONT SIZE=2>> > this work well for me, then it might work for someone else as well.</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> > On the subject of developing a single interface to all database from *</FONT>
<BR><FONT SIZE=2>> > dialplans - what about unix ODBC and commands like</FONT>
<BR><FONT SIZE=2>> > ODBC(Connect DSN connID ...)</FONT>
<BR><FONT SIZE=2>> > ODBC(Query ${connID} resultID ...)</FONT>
<BR><FONT SIZE=2>> > ODBC(Fetch ${resultID} fetchID...)</FONT>
<BR><FONT SIZE=2>> > ODBC(Disconnect ${connID} ...)</FONT>
<BR><FONT SIZE=2>> > ODBC(Clear${resultID}</FONT>
<BR><FONT SIZE=2>> > would they be generic enough?</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> ODBC is horribly inefficient. I wouldn't go near it. Perhaps a</FONT>
<BR><FONT SIZE=2>> more generic interface would be better. Something like the</FONT>
<BR><FONT SIZE=2>> following:</FONT>
</P>
<P><FONT SIZE=2>Yes, I agree, and app_sql_mysql and others would be much faster if app_sql connect to database when modul loaded,</FONT>
<BR><FONT SIZE=2>and keep the connection open. </FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 6</FONT>
<BR><FONT SIZE=2>From: Andrew Kohlsmith <akohlsmith-asterisk@benshaw.com></FONT>
<BR><FONT SIZE=2>Organization: Benshaw Canada</FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>Date: Tue, 3 Aug 2004 05:43:45 -0400</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>On Monday 02 August 2004 21:46, Kevin Walsh wrote:</FONT>
<BR><FONT SIZE=2>> ODBC is horribly inefficient. I wouldn't go near it. Perhaps a</FONT>
<BR><FONT SIZE=2>> more generic interface would be better. Something like the</FONT>
<BR><FONT SIZE=2>> following:</FONT>
</P>
<P><FONT SIZE=2>How hard will even a busy 8-PRI box hit the DB? I can't imagine ODBC being </FONT>
<BR><FONT SIZE=2>less efficient than accessing a large flat file! I will come forward right </FONT>
<BR><FONT SIZE=2>now and say I don't have any hard numbers myself (hence my reason for </FONT>
<BR><FONT SIZE=2>asking), but let's not talk efficiencies on a stable, proven DB abstraction </FONT>
<BR><FONT SIZE=2>system until they start to become the bottleneck... </FONT>
</P>
<P><FONT SIZE=2>> The various "database drivers" could be implemented as loadable</FONT>
<BR><FONT SIZE=2>> modules, much like the codecs and applications etc.</FONT>
</P>
<P><FONT SIZE=2>Isn't this pretty much how ODBC works anyway? You're just moving the </FONT>
<BR><FONT SIZE=2>abstraction to another place (and having to write it yourself now, too).</FONT>
</P>
<P><FONT SIZE=2>Regards,</FONT>
<BR><FONT SIZE=2>Andrew</FONT>
</P>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 7</FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>From: Steven Critchfield <critch@basesys.com></FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Date: Tue, 03 Aug 2004 06:15:17 -0500</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>On Tue, 2004-08-03 at 04:43, Andrew Kohlsmith wrote:</FONT>
<BR><FONT SIZE=2>> On Monday 02 August 2004 21:46, Kevin Walsh wrote:</FONT>
<BR><FONT SIZE=2>> > ODBC is horribly inefficient. I wouldn't go near it. Perhaps a</FONT>
<BR><FONT SIZE=2>> > more generic interface would be better. Something like the</FONT>
<BR><FONT SIZE=2>> > following:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> How hard will even a busy 8-PRI box hit the DB? I can't imagine ODBC being </FONT>
<BR><FONT SIZE=2>> less efficient than accessing a large flat file! I will come forward right </FONT>
<BR><FONT SIZE=2>> now and say I don't have any hard numbers myself (hence my reason for </FONT>
<BR><FONT SIZE=2>> asking),</FONT>
</P>
<P><FONT SIZE=2>Who would access a large flat file anyways. Dialplans are all stored in</FONT>
<BR><FONT SIZE=2>memory and only read in at startup or reload times. I dare you to find</FONT>
<BR><FONT SIZE=2>any number saying that an access to an external process running any SQL</FONT>
<BR><FONT SIZE=2>interpreter to be faster than a memory lookup in the original calling</FONT>
<BR><FONT SIZE=2>processes memory space.</FONT>
<BR><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Steven Critchfield <critch@basesys.com></FONT>
</P>
<BR>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 8</FONT>
<BR><FONT SIZE=2>From: Andrew Kohlsmith <akohlsmith-asterisk@benshaw.com></FONT>
<BR><FONT SIZE=2>Organization: Benshaw Canada</FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>Date: Tue, 3 Aug 2004 07:30:20 -0400</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>On Tuesday 03 August 2004 07:15, Steven Critchfield wrote:</FONT>
<BR><FONT SIZE=2>> Who would access a large flat file anyways. Dialplans are all stored in</FONT>
<BR><FONT SIZE=2>> memory and only read in at startup or reload times. I dare you to find</FONT>
<BR><FONT SIZE=2>> any number saying that an access to an external process running any SQL</FONT>
<BR><FONT SIZE=2>> interpreter to be faster than a memory lookup in the original calling</FONT>
<BR><FONT SIZE=2>> processes memory space.</FONT>
</P>
<P><FONT SIZE=2>Well duh, that's like saying "I dare you to prove that water is wet!"</FONT>
</P>
<P><FONT SIZE=2>I was referring more to the request that we as a community write our own </FONT>
<BR><FONT SIZE=2>custom DB drivers for all the DBs we want to support instead of using ODBC.</FONT>
</P>
<P><FONT SIZE=2>-A.</FONT>
</P>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 9</FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>From: Steven Critchfield <critch@basesys.com></FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Date: Tue, 03 Aug 2004 06:42:17 -0500</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>On Tue, 2004-08-03 at 06:30, Andrew Kohlsmith wrote:</FONT>
<BR><FONT SIZE=2>> On Tuesday 03 August 2004 07:15, Steven Critchfield wrote:</FONT>
<BR><FONT SIZE=2>> > Who would access a large flat file anyways. Dialplans are all stored in</FONT>
<BR><FONT SIZE=2>> > memory and only read in at startup or reload times. I dare you to find</FONT>
<BR><FONT SIZE=2>> > any number saying that an access to an external process running any SQL</FONT>
<BR><FONT SIZE=2>> > interpreter to be faster than a memory lookup in the original calling</FONT>
<BR><FONT SIZE=2>> > processes memory space.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Well duh, that's like saying "I dare you to prove that water is wet!"</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I was referring more to the request that we as a community write our own </FONT>
<BR><FONT SIZE=2>> custom DB drivers for all the DBs we want to support instead of using ODBC.</FONT>
</P>
<P><FONT SIZE=2>res_data? Remember that project? Should be around here somewhere.</FONT>
</P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Steven Critchfield <critch@basesys.com></FONT>
</P>
<BR>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 10</FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Dev] RE: MYSQL application</FONT>
<BR><FONT SIZE=2>From: Domjan Attila <adomjan@tvnet.hu></FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Date: Tue, 03 Aug 2004 14:23:32 +0200</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>On Tue, 2004-08-03 at 13:15, Steven Critchfield wrote:</FONT>
<BR><FONT SIZE=2>> On Tue, 2004-08-03 at 04:43, Andrew Kohlsmith wrote:</FONT>
<BR><FONT SIZE=2>> > On Monday 02 August 2004 21:46, Kevin Walsh wrote:</FONT>
<BR><FONT SIZE=2>> > > ODBC is horribly inefficient. I wouldn't go near it. Perhaps a</FONT>
<BR><FONT SIZE=2>> > > more generic interface would be better. Something like the</FONT>
<BR><FONT SIZE=2>> > > following:</FONT>
<BR><FONT SIZE=2>> > </FONT>
<BR><FONT SIZE=2>> > How hard will even a busy 8-PRI box hit the DB? I can't imagine ODBC being </FONT>
<BR><FONT SIZE=2>> > less efficient than accessing a large flat file! I will come forward right </FONT>
<BR><FONT SIZE=2>> > now and say I don't have any hard numbers myself (hence my reason for </FONT>
<BR><FONT SIZE=2>> > asking),</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Who would access a large flat file anyways. Dialplans are all stored in</FONT>
<BR><FONT SIZE=2>> memory and only read in at startup or reload times. I dare you to find</FONT>
<BR><FONT SIZE=2>> any number saying that an access to an external process running any SQL</FONT>
<BR><FONT SIZE=2>> interpreter to be faster than a memory lookup in the original calling</FONT>
<BR><FONT SIZE=2>> processes memory space.</FONT>
</P>
<P><FONT SIZE=2>And if you have 50000+ lines in extensions.conf u will wait minutes for</FONT>
<BR><FONT SIZE=2>reload and use lot of memory...</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 11</FONT>
<BR><FONT SIZE=2>Date: Tue, 3 Aug 2004 15:58:18 +0300</FONT>
<BR><FONT SIZE=2>From: Serkan Albayrak <albayraks2@itu.edu.tr></FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Subject: [Asterisk-Dev] minumum linux hardware-less than 100 mb</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Hello, </FONT>
</P>
<P><FONT SIZE=2>We are rying to build an asterisk system, but now we want to learn what is the </FONT>
<BR><FONT SIZE=2>minumum disk space to install linux+ asterisk and make those work properly.In </FONT>
<BR><FONT SIZE=2>fact, we are trying to put those in a SBC (single board computer)included a </FONT>
<BR><FONT SIZE=2>maximum 128mb flash memory. Do you know any companies which sell embedded linux </FONT>
<BR><FONT SIZE=2>boards for Asterisk? Thanks....</FONT>
</P>
<P><FONT SIZE=2>Serkan Albayrak</FONT>
</P>
<P><FONT SIZE=2>Electronics and Comm. Eng</FONT>
</P>
<P><FONT SIZE=2>-------------------------------------------------</FONT>
<BR><FONT SIZE=2>This mail sent through IMP: <A HREF="http://webmail.students.itu.edu.tr" TARGET="_blank">http://webmail.students.itu.edu.tr</A></FONT>
</P>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 12</FONT>
<BR><FONT SIZE=2>From: Andrew Kohlsmith <akohlsmith-asterisk@benshaw.com></FONT>
<BR><FONT SIZE=2>Organization: Benshaw Canada</FONT>
<BR><FONT SIZE=2>To: asterisk-dev@lists.digium.com</FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Dev] minumum linux hardware-less than 100 mb</FONT>
<BR><FONT SIZE=2>Date: Tue, 3 Aug 2004 09:38:22 -0400</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2>On Tuesday 03 August 2004 08:58, Serkan Albayrak wrote:</FONT>
<BR><FONT SIZE=2>> We are rying to build an asterisk system, but now we want to learn what is</FONT>
<BR><FONT SIZE=2>> the minumum disk space to install linux+ asterisk and make those work</FONT>
<BR><FONT SIZE=2>> properly.In fact, we are trying to put those in a SBC (single board</FONT>
<BR><FONT SIZE=2>> computer)included a maximum 128mb flash memory. Do you know any companies</FONT>
<BR><FONT SIZE=2>> which sell embedded linux boards for Asterisk? Thanks....</FONT>
</P>
<P><FONT SIZE=2>I have fit Linux (including Perl, IPSEC, iproute2 and other goodies) into a=</FONT>
<BR><FONT SIZE=2>=20</FONT>
<BR><FONT SIZE=2>16M CF card. Asterisk is TINY compared to the 40MB Perl install I had in=20</FONT>
<BR><FONT SIZE=2>there.</FONT>
</P>
<P><FONT SIZE=2>I can help you with it, or you can go out on your own and try -- I used Lin=</FONT>
<BR><FONT SIZE=2>ux=20</FONT>
<BR><FONT SIZE=2>=46rom Scratch (<A HREF="http://www.linuxfromscratch.org" TARGET="_blank">http://www.linuxfromscratch.org</A>) but there is also the tuxr=</FONT>
<BR><FONT SIZE=2>oot=20</FONT>
<BR><FONT SIZE=2>buildkit which seems to be the "more better" way of doing it these days. Y=</FONT>
<BR><FONT SIZE=2>ou=20</FONT>
<BR><FONT SIZE=2>can also check out the openwrt distribution (<A HREF="http://www.openwrt.org" TARGET="_blank">http://www.openwrt.org</A>) and=20</FONT>
<BR><FONT SIZE=2>customize it to include the Zap drivers and Asterisk. =20</FONT>
</P>
<P><FONT SIZE=2>Contact me offlist if you would like any more assistance on this -- I think=</FONT>
<BR><FONT SIZE=2>=20</FONT>
<BR><FONT SIZE=2>you will find though that it is quite easy to make small versions of Linux=</FONT>
<BR><FONT SIZE=2>=20</FONT>
<BR><FONT SIZE=2>and that Asterisk plays nicely in confined environments. :-)</FONT>
</P>
<P><FONT SIZE=2>Regards,</FONT>
<BR><FONT SIZE=2>Andrew</FONT>
</P>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>Message: 13</FONT>
<BR><FONT SIZE=2>Date: Tue, 3 Aug 2004 17:05:46 +0200</FONT>
<BR><FONT SIZE=2>From: Miroslav Nachev <miro@space-comm.com></FONT>
<BR><FONT SIZE=2>Organization: COSMOS Software Enterprises, Ltd.</FONT>
<BR><FONT SIZE=2>To: Serkan Albayrak <asterisk-dev@lists.digium.com></FONT>
<BR><FONT SIZE=2>Subject: Re: [Asterisk-Dev] minumum linux hardware-less than 100 mb</FONT>
<BR><FONT SIZE=2>Reply-To: asterisk-dev@lists.digium.com</FONT>
</P>
<P><FONT SIZE=2> Dear Serkan,</FONT>
</P>
<P><FONT SIZE=2> You can try:</FONT>
<BR><FONT SIZE=2> 1. AMD Geode NX DB1500 Development Board</FONT>
<BR><FONT SIZE=2> - RAM: 1 x DIMM up to 1 GB DDR DRAM module;</FONT>
<BR><FONT SIZE=2> - Flash: up to 512MB FLASH memory;</FONT>
<BR><FONT SIZE=2> - One PCI 2.3 Expansion Slot;</FONT>
<BR><FONT SIZE=2> - Debug Assist Features ...;</FONT>
<BR><FONT SIZE=2> - On-Board Peripherals: LAN, USB, IDE, SATA, CRT, AC'97 Audio,</FONT>
<BR><FONT SIZE=2> etc.</FONT>
<BR><FONT SIZE=2> 2. AMD Alchemy DBAu1550 Development Board</FONT>
<BR><FONT SIZE=2> - RAM: 192MB DDR;</FONT>
<BR><FONT SIZE=2> - Flash: 192 MB - 64MB Boot, 64MB Parameter, 64MB NAND Flash</FONT>
<BR><FONT SIZE=2> memory;</FONT>
<BR><FONT SIZE=2> - Two hot-swappable PCMCIA slots;</FONT>
<BR><FONT SIZE=2> - Static memory interface connector;</FONT>
<BR><FONT SIZE=2> - IDE ATA/133 connector;</FONT>
<BR><FONT SIZE=2> - Two 3.3V/PCI connectors;</FONT>
<BR><FONT SIZE=2> - Debug assist features;</FONT>
<BR><FONT SIZE=2> - 2 x LAN 10/100;</FONT>
<BR><FONT SIZE=2> - USB, Serials, AC'97 Audio, etc;</FONT>
<BR><FONT SIZE=2> - Power over Ethernet.</FONT>
</P>
<BR>
<P><FONT SIZE=2> Best Regards,</FONT>
<BR><FONT SIZE=2> Miroslav Nachev</FONT>
</P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Hello, </FONT>
</P>
<P><FONT SIZE=2>We are rying to build an asterisk system, but now we want to learn what is the </FONT>
<BR><FONT SIZE=2>minumum disk space to install linux+ asterisk and make those work properly.In </FONT>
<BR><FONT SIZE=2>fact, we are trying to put those in a SBC (single board computer)included a </FONT>
<BR><FONT SIZE=2>maximum 128mb flash memory. Do you know any companies which sell embedded linux </FONT>
<BR><FONT SIZE=2>boards for Asterisk? Thanks....</FONT>
</P>
<P><FONT SIZE=2>Serkan Albayrak</FONT>
</P>
<P><FONT SIZE=2>Electronics and Comm. Eng</FONT>
</P>
<P><FONT SIZE=2>-------------------------------------------------</FONT>
<BR><FONT SIZE=2>This mail sent through IMP: <A HREF="http://webmail.students.itu.edu.tr" TARGET="_blank">http://webmail.students.itu.edu.tr</A></FONT>
<BR><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>Asterisk-Dev mailing list</FONT>
<BR><FONT SIZE=2>Asterisk-Dev@lists.digium.com</FONT>
<BR><FONT SIZE=2><A HREF="http://lists.digium.com/mailman/listinfo/asterisk-dev" TARGET="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</A></FONT>
<BR><FONT SIZE=2>To UNSUBSCRIBE or update options visit:</FONT>
<BR><FONT SIZE=2> <A HREF="http://lists.digium.com/mailman/listinfo/asterisk-dev" TARGET="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</A></FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>--__--__--</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>Asterisk-Dev mailing list</FONT>
<BR><FONT SIZE=2>Asterisk-Dev@lists.digium.com</FONT>
<BR><FONT SIZE=2><A HREF="http://lists.digium.com/mailman/listinfo/asterisk-dev" TARGET="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</A></FONT>
</P>
<BR>
<P><FONT SIZE=2>End of Asterisk-Dev Digest</FONT>
</P>
</BODY>
</HTML>