Chris, While you are thinking logically, This will just as un-effective as putting them all in the dialplan, as the DBGet() and DBPut() functionality deals with the internal astdb (db1 database).

I would reccomend going the AGI route at this time, until we have better functionality for DB handling.

-Josh

Chris Shaw wrote:

Why use AGI? Why not just use the builtin DBGet() and DBPut() functions in
*?

   -Chris

----- Original Message -----
From: "drodden" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 10, 2004 9:22 AM
Subject: [Asterisk-Users] Blocking the 'Do Not Call" List




Anybody have any experience with blocking numbers in the U.S's Do Not
Call list?

We have a customer that will be getting their own Asterisk server from
us, and they want it to be check outbound numbers against the do not
call list; this is for a backup, in case there's a slip up and one of
their people try to dial somebody on the do not call list.

The list has millions of numbers, and I don't think the extensions.conf
file could handle me listing all million+ phone numbers and making it
play a sound like "That number is on the do not call list", and then
creating a _NXXNXXNXXX extension at the very bottom. The list would take
up all it's memory. Anybody have a more elegant solution? Maybe an AGI
script to match the outbound phone number against a column in a table in
a MySQL database? Is there something similar already written that I can
just modify?


_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to