Hi Nick, Understand your reasoning - though as Matt points out sql db isn't in the core so compiling it there would preclude seemless upgrades. Also, I personally would be concerned putting the calls right into the call-file thread might create an issue if you hung on a db query or insert. Finally (and I'd love to hear the answer not knowing), but I believe "normally-initiated/instantiated" calls are handled with direct calls via either SIP requests and/or AMI - thus even using the proposed method, I *think* the db/file-drop method is going to create some overhead that might not scale well...
Best, David -----Original Message----- From: Nick Khamis <sym...@gmail.com> To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users@lists.digium.com> Date: Mon, 26 Sep 2011 18:49:07 -0400 Subject: Re: [asterisk-users] Asterisk Realtime Time Dial App Hello David, Thank you so much for your response. I am sure it can be easily done using AGI. The reason I am leaning more towards storing the call information in a database record, is because our existing client applications can be easily modified to write to MySQL. The asterisk cron/thread that would querying the DB should be no different than existing implementation used process the call files? For those of you that may be interested in what we are doing. We are developing an application that will apply NLP services on text generated using the speech to text module, and generate the response that will then be forwarded to the text to speech. Cheers, Nick .
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
