Ticket #2819 (closed Bugs: worksforme)

Opened 8 months ago

Last modified 8 months ago

Blacklist does not work in 2.4

Reported by: terrizzi Assigned to:
Priority: major Milestone: 2.5
Component: Other Module Version: 2.4-branch
Keywords: Cc:
Confirmation: Need Feedback SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

When blacklisting a number, the system still accepts the call from the CID.

I set the priority high because I have stalkers calling my employees, and its causing a huge disruption in business.

Thanks Guys

Change History

05/13/08 09:31:06 changed by terrizzi

I tried blacklisting my own cell phone and it did not work.

05/13/08 14:11:51 changed by pnlarsson

  • owner deleted.
  • component changed from - choose - to Other Module.

Do you have a CLI output of: 

lisa*CLI> database show blacklist

And when the inbound call is not blacklisted?

05/14/08 06:02:41 changed by terrizzi

database show blacklist

/blacklist/4447784208 : 1

Im not sure about the second question.

Numbers are being added and deleted properly, with freepbx gui and feature code, but not actually blocking the number to inbound route or direct DID

05/14/08 07:36:10 changed by p_lindheimer

please capture a CLI trace of the blocked call coming in to see if it is coming in a different format the you input it.

05/14/08 10:47:32 changed by terrizzi

It is not. I have added multiple formats, via feature code to block last caller and using add _ incase it was comming in with a 1.

05/14/08 10:53:03 changed by terrizzi

also see this: http://freepbx.org/forum/freepbx/users/blacklist-not-working-0

app blacklist just doesnt match the caller ID, for inbound DID extensions, also If i make a inbound route for a specific call ID it doesnt to pick it up in the dial plan, it gets routed directly to the extension.

05/14/08 11:07:28 changed by p_lindheimer

  • confirmation changed from Unreviewed to Need Feedback.

terrizzi, "It is not." is not a CLI trace. If you would like people to address this bug, you need to help us figure it out by providing the data. The trace will be helpful. If the trace shows that all should be correct, then it will show specifically what is happening so we can see if there is an issue with FreePBX or with Asterisk since the blacklist is effectively a core asterisk function. If the trace shows the format is correct, please also include the log trace in addition to the CLI trace, and set verbosity to about 5. Lastly, Modify the auto-generated function app-blacklist-check in extensions_additional.conf as follows: 

[app-blacklist-check]
include => app-blacklist-check-custom
exten => s,1,LookupBlacklist()

; DEBUG - THIS IS THE NEW LINE TO INSERT HERE:
;
exten => s,n,Noop(GOT LOOKUPBLSTATUS: ${LOOKUPBLSTATUS}) ;NOTE THIS LINE IS ADDED
;

exten => s,n,GotoIf($["${LOOKUPBLSTATUS}"="FOUND"]?blacklisted)
exten => s,n,Return()
exten => s,n(blacklisted),Answer
exten => s,n,Wait(1)
exten => s,n,Zapateller()
exten => s,n,Playback(ss-noservice)
exten => s,n,Hangup

; end of [app-blacklist-check]

and after adding that line, make sure to do a reload at the cli so it takes, and don't make any changes in the GUI that will overwrite it. This will help provdide additional debug data.

05/15/08 09:11:50 changed by terrizzi

Instead of doing a CLI trace I did do the following to make it work.

Uninstalled the blacklist module. Reload the Config Reinstall/Enable the blacklist module.

It seems when i installed the module the first time I did it in a large sweep with all the other modules. Install it by itself fixed the problem. I dont know if this affected anything yet.

05/15/08 10:00:54 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to worksforme.
  • milestone changed from Cut Line to 3.0.

should not make a difference, it is either installed or not since bulk installation just installs everything one at a time anyhow? In any event, I'm glad you have it working. Thanks for the update.