Summary: | ASTERISK-30137: manager: Global disabled event filtered is incomplete | ||
Reporter: | N A (InterLinked) | Labels: | |
Date Opened: | 2022-07-12 16:35:04 | Date Closed: | 2022-07-19 09:53:03 |
Priority: | Minor | Regression? | |
Status: | Closed/Complete | Components: | Core/ManagerInterface |
Versions: | 18.13.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Attachments: | ||
Description: | There are 2 paths that AMI events can take in going out to manager sessions.
The globally disabled event filtering is currently only happening on one of them, so events from stasis, for example, aren't globally disabled even if they're supposed to be. Additionally, the manager show settings command truncates the list of disabled events (and variable names). This is adjusted so that the entire list is printed out fully. | ||
Comments: | By: Asterisk Team (asteriskteam) 2022-07-12 16:35:05.492-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. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Friendly Automation (friendly-automation) 2022-07-19 09:53:04.387-0500 Change 18846 merged by Friendly Automation: manager: Fix incomplete filtering of AMI events. [https://gerrit.asterisk.org/c/asterisk/+/18846|https://gerrit.asterisk.org/c/asterisk/+/18846] By: Friendly Automation (friendly-automation) 2022-07-20 09:47:56.450-0500 Change 18844 merged by George Joseph: manager: Fix incomplete filtering of AMI events. [https://gerrit.asterisk.org/c/asterisk/+/18844|https://gerrit.asterisk.org/c/asterisk/+/18844] By: Friendly Automation (friendly-automation) 2022-07-20 09:48:15.968-0500 Change 18845 merged by George Joseph: manager: Fix incomplete filtering of AMI events. [https://gerrit.asterisk.org/c/asterisk/+/18845|https://gerrit.asterisk.org/c/asterisk/+/18845] By: Friendly Automation (friendly-automation) 2022-07-20 12:29:25.476-0500 Change 18852 merged by Friendly Automation: manager: Fix incomplete filtering of AMI events. [https://gerrit.asterisk.org/c/asterisk/+/18852|https://gerrit.asterisk.org/c/asterisk/+/18852] By: Friendly Automation (friendly-automation) 2022-07-20 12:55:17.067-0500 Change 18821 merged by Joshua Colp: manager: Fix incomplete filtering of AMI events. [https://gerrit.asterisk.org/c/asterisk/+/18821|https://gerrit.asterisk.org/c/asterisk/+/18821] |