Summary:	ASTERISK-29072: Manager EventFilter(Blacklist) not working
Reporter:	Neimar Avila (neimar.avila)	Labels:
Date Opened:	2020-09-08 09:50:16	Date Closed:	2020-09-16 10:40:59
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Core/ManagerInterface
Versions:	16.13.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	Centos 7 x64	Attachments:
Description:	Hello, good day to you. Using the event filter (blacklist) to not display some types, is not working. manager.conf [vsphone3] secret = ***** permit=127.0.0.1/255.255.255.255 writetimeout = 100 read = all write = all eventfilter=!Event: NewCallerId eventfilter=!Event: NewExten eventfilter=!Event: Newchannel eventfilter=!Event: NewConnectedLine eventfilter=!Event: DTMFBegin eventfilter=!Event: DTMFEnd eventfilter=!Event: MusicOnHoldStart eventfilter=!Event: MusicOnHoldStop eventfilter=!Event: AGIExecStart eventfilter=!Event: AGIExecEnd eventfilter=!Event: DeviceStateChange eventfilter=!Event: Dial eventfilter=!Event: DialBegin eventfilter=!Event: DialEnd Using telnet: Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Asterisk Call Manager/5.0.2 Action: login Username: vsphone3 Secret: ***** Events: on Response: Success Message: Authentication accepted Event: Newexten Privilege: dialplan,all Channel: SIP/CA70C2C6635A-00000010 ChannelState: 4 ChannelStateDesc: Ring CallerIDNum: 1000 CallerIDName: RAMAL_1000 ConnectedLineNum: <unknown> ConnectedLineName: <unknown> Language: en AccountCode: Context: hmlvirtual_ramal_1000 Exten: 031984952402 Priority: 1 Uniqueid: 1599574412.16 Linkedid: 1599574412.16 Extension: 031984952402 Application: Verbose AppData: 1, Rota SAIDA_PADRAO
Comments:	By: Asterisk Team (asteriskteam) 2020-09-08 09:50:17.546-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Benjamin Keith Ford (bford) 2020-09-08 11:05:05.718-0500 It looks like you have a capitalization error for the event. In your {{manager.conf}}, you have: {code} eventfilter=!Event: NewExten {code} The actual event is: {code} Event: Newexten {code} "Exten" should not be capitalized. Does this fix the problem? By: Neimar Avila (neimar.avila) 2020-09-16 10:35:19.089-0500 Hi Benjamin, sorry. My fault, probably I need new eyes. Thanks again. By: Asterisk Team (asteriskteam) 2020-09-16 10:35:19.483-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Benjamin Keith Ford (bford) 2020-09-16 10:40:59.738-0500 Happy to help! I'll go ahead and close this issue.