[Asterisk-Dev] Some (lack of) answers regarding the wakeup call application...

[Eric Wieling]

My callback and vmoutcall scripts schedule an outgoing call for the
future using only the features of Asterisk::AGI.  Here is a link to my
downloads directory:  http://www.fnords.org/~eric/asterisk/downloads

On Tue, 2004-06-01 at 10:27, Rob Fugina wrote:
> Since I only seem to get questions, and no feedback, from the Wiki page,
> I'll ask here.  There seems to be no lack of opinions here...
> 
> I have a working wakeup call system on my home * system.  The architecture
> is something I'm not perfectly happy with, though.  There are two AGI
> scripts, written in Perl, which handle (a) scheduling, confirming,
> and cancelling a wakeup call, and (b) the wakeup call itself, with the
> option to snooze for 5, 15, or 30 minutes.
> 
> The Perl scripts use the Asterisk::AGI module I came across months ago,
> but by necessity, can't use the Asterisk/Perl code for creating call files
> -- it has a habit of creating them right in the outgoing call queue,
> generating a call immediately.  So the Perl code creates call files in
> a wakeup queue directory, and a cron job (a shell script) runs every
> minute looking for wakeup calls in the queue that need to be handled,
> and moves them to the outgoing call queue.
> 
> It has occurred to me that the two AGI scripts could be rewritten as real
> compiled asterisk applications, but then it always hits me that without
> some kind of cron-line built-in scheduler, or changes to the outgoing
> call queueing that would allow a call to be scheduled for the future,
> there would still be that external cron-driven shell script.  Ugly.
> 
> What I'm wondering is this:  Is there enough interest in the new features
> I mentioned (either an internal scheduler or scheduled outgoing calls)
> that I should work on a C version of the wakeup AGI scripts, or should
> my (impending) next rewrite maintain the current architecture?
> 
> Anyone with specific questions about using my wakeup app, please email
> me directly.
> 
> Rob
-- 
          Eric Wieling * BTEL Consulting * 504-899-1387 x2111
"In a related story, the IRS has recently ruled that the cost of Windows
upgrades can NOT be deducted as a gambling loss."