Summary:	ASTERISK-00225: blacklists
Reporter:	jrollyson (jrollyson)	Labels:
Date Opened:	2003-09-05 02:23:00	Date Closed:	2011-06-07 14:05:15
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	an interface to an external blacklisted number database would be nice, with ability to deny calls from coming in from specified numbers, or to deny calls from being placed to specifed numbers... Possible applications for this are: - DO NOT CALL lists that telemarketers are required to keep (although, do we really want to support telemarketing applications ;) - Banned callers list of telemarketers or abusive callers.
Comments:	By: John Todd (jtodd) 2003-09-06 02:42:28 1) Sounds like this is a feature request, not a bug. 2) This could easily be done with an AGI script; use whatever database you want.  There is no clear reason why this needs to be incorporated into the main code body (though it would make a very nice addition to the new "contrib" directory) 3) Have you seen this? localhost*CLI> show application LookupBlacklist localhost*CLI>  -= Info about application 'LookupBlacklist' =- [Synopsis]:  Look up Caller*ID name/number from blacklist database [Description]:  LookupBlacklist: Looks up the Caller*ID number on the active channel in the Asterisk database (family 'blacklist').  If the number is found, and if there exists a priority n + 101, where 'n' is the priority of the current instance, then  the channel  will  be  setup  to continue at that priority level. Otherwise, it returns 0.  Does nothing if no Caller*ID was received on the channel. Example: database put blacklist <name/number> 1 localhost*CLI> By: John Todd (jtodd) 2003-09-08 15:03:41 closing due to the fact that this can be implemented with other methods.   Perhaps someone can post some examples on the list... jrollyson - you might try asking the -users list to see if someone can forward their scripts, if they have them.