<div dir="ltr"><div>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. <br>
<br></div>-Josh<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 23, 2014 at 4:12 AM, James Sharp <span dir="ltr"><<a href="mailto:james@fivecats.org" target="_blank">james@fivecats.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 4/23/2014 12:20 AM, Nick Cameo wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
That's about as simple as it gets.<br>
<br>
A call file that goes to the dialplan.<br>
<br>
A dialplan that consists of Read (which would play the message)<br>
followed a GotoIf into a mailbox (either voicemail or Dial() to an<br>
external number).<br>
<br>
One hint for doing unattended dialing like this, make sure you're<br>
dialing using a SIP or other digital method rather than, say, out an<br>
analogue port that doesn't have decent answer detect.<br>
<br>
And you can't just dump a whole bunch of call files into the system<br>
at once, you'll need to meter them out based on the number of<br>
concurrent outbound calls your provider will allow.<br>
<br>
<br>
Hello James,<br>
<br>
Good to see you here, and thank you very much. Though my basic idea of<br>
how it will look using call files and dialplan is like what you and<br>
others on here have pointed out. Yes,<br>
we are using SIP for both origination and termination (just helping my<br>
friend use some of our accounts used for PBX, and prepaid). I have been<br>
using * for many years now however,<br>
never for call center/predictive dialer type processes. Once I have got<br>
this thing to call out and get calls coming in. It would be nice to<br>
write to a database all the users that press<br>
option on. I have a strong Java, PHP and SQL background. Will probably<br>
need to make a call using AGI or such?<br>
<br>
N.<br>
<br>
<br>
</blockquote>
<br></div></div>
You can go AGI, but there are direct ODBC handles available in the dialplan if you build Asterisk properly with the ODBC resources enabled. That'd my personal preference from a performance standpoint.<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
<br>
-- <br>
______________________________<u></u>______________________________<u></u>_________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/<u></u>mailman/listinfo/asterisk-<u></u>users</a><br>
</div></div></blockquote></div><br></div>