VoIP Mailing List Archives

[joshdmetzger at gmail.com]

I agree that ODBC is the way to go here.  It's trivially easy to setup, and equally simple to push database updates via the dialplan.  I've used ODBC connectivity with Asterisk in a large and VERY busy call center, and performance was never remotely an issue (call recording is a different story, but that's something else entirely...).  There was mention of checking against a DNC list, and ODBC would be good for this as well - just put that into a table and match against it before making your outbound call. 


-Josh



On Wed, Apr 23, 2014 at 4:12 AM, James Sharp <james@fivecats.org (james@fivecats.org)> wrote:

[asterisk.org at sedwar...]

On 4/23/2014 12:20 AM, Nick Cameo wrote:

[support at drdos.info]

[joshdmetzger at gmail.com]

I've always done my DB access via func_odbc and not with the mysql package.  While we ran a MySQL db, I was more comfortable with the odbc stuff because it was part of Asterisk core and not an addon package.  I can't speak to the simplicity of using the mysql stuff vs the odbc stuff, but there isn't a lot to creating your query in func_odbc and then calling it from your dialplan (and passing a few variables).  I'd say it's no more difficult than calling an AGI, in my case we WERE processing a LARGE volume of calls, and importantly: It didn't require me to learn C or PHP. 

Now if you want complicated, somewhere I have a very long GotoIf() that includes an ODBC call and nested Math() functions...


-Josh



On Wed, Apr 23, 2014 at 11:17 AM, Doug Lytle <support@drdos.info (support@drdos.info)> wrote:

[asterisk.org at sedwar...]

On Tue, 22 Apr 2014, A J Stiles wrote:

[asterisk.org at sedwar...]

On Wed, 23 Apr 2014, Steve Edwards wrote:

[joshdmetzger at gmail.com]

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 scheduling"...


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).


-Josh



On Wed, Apr 23, 2014 at 2:36 PM, Steve Edwards <asterisk.org@sedwards.com (asterisk.org@sedwards.com)> wrote:

[asterisk_list at earth...]

On Wednesday 23 Apr 2014, Steve Edwards wrote: