[asterisk-users] Open Source Asterisk Polling Solution
joshdmetzger at gmail.com
Wed Apr 23 13:48:14 CDT 2014
I think it's all a matter of personal taste. I think the logic for "add to
DNC" is extremely trivial and would be more complicated with an AGI. You
have your prompt playback/read, if they hit "1", head to the queue, if they
hit "2", it's a single dialplan line to put the info into the database and
then one more like to Playback a nice "Goodbye" message. You also add one
additional line before calling out in that case - one query for the
national DNC and one for the "internal" DNC, or you can get really fancy
and setup your table with an extra column that denotes "national" or
"internal". While you're add it, throw in that extra column for "next call
All that being said, you would probably be better off pre-processing before
sending the phone numbers to the PBX so you've already scrubbed the call
list to only people not on a DNC list and within the scheduled call-back
time. That way you save the checks for each call outbound and only have
the code for adding people to the DNC and scheduling the next call, though
it still could be done either way (though in the case of not
pre-processing, you're getting closer to making Asterisk into a dialer
system and then you can get into fancy legal issues about using an
"autodialer" when you accidentally call someone who doesn't want to be
called and they complain (dependant on jurisdiction).
On Wed, Apr 23, 2014 at 2:36 PM, Steve Edwards <asterisk.org at sedwards.com>wrote:
> On Wed, 23 Apr 2014, Steve Edwards wrote:
> I tried database access in the dialplan using the mysql() application
>>>> years ago, just to confirm I was right and I was :) What an ugly, messy,
>>>> fragile dialplan.
> On Wed, 23 Apr 2014, Doug Lytle wrote:
> With FuncODBC this is no longer an issue. All of the query logic is
>> handled outside of the dial plan.
> I took a look and it looks like a step in the right direction, kind of a
> 'prepared statement' approach and it gets all the ugly quoting nonsense out
> of the dialplan. The query statement may be out of the dialplan, but the
> logic of what to do with the returned values remains.
> The OP stated that he was going to 'will wire it up to the DNC' (the
> National Do Not Call Registry?) which sounds like a simple 'query the
> database to see if the key exists' kind of thing for which ODBC seems
> This application should be expanded to include multiple databases so his
> callers can press 1 to be queued for an agent or 2 to be added to his
> client's private DNC database. While checking 2 databases is no big deal, a
> simple 'check-dnc' AGI can hide those details and yield a cleaner dialplan.
> As the application matures, there may be additional enhancements that
> would lean towards wishing he had started down the AGI road.
> If the target list includes (but is not limited to) members of a group
> (like a church) you could have a situation where the callee is on the DNC,
> but has opted-in so you have another database to consider.
> How about checking the database to see the last time they had 'waste they
> need picked up?' If the 'waste' is charitable donations of clothing or
> furniture, I suspect most people would be good with just a call or 2 per
> How about letting the 'donor' schedule the number of months until the next
> Thanks in advance,
> Steve Edwards sedwards at sedwards.com Voice: +1-760-468-3867 PST
> Newline Fax: +1-760-731-3000
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-users