Add AMI Event Filtering documentation #162
Conversation
|
jcolp disclaimer ai and hi was used |
|
https://docs.asterisk.org/Configuration/Interfaces/Asterisk-Manager-Interface-AMI/AMI-v2-Specification/?h=#general-settings
|
|
It can be updated, yes, though would need explicit statement about which versions the new stuff was added to. |
|
can you point to me how i can check to which version this was applied ? |
|
What I would do is look at the date it was merged. I would then find the releases that occurred after such date and check the release notes to see if it was mentioned. |
|
https://downloads.asterisk.org/pub/telephony/asterisk/old-releases/ Asterisk 18: 18.25.0 (released October 17, 2024) |
|
Nope. It's not in those. It's in the releases after, as shown in the corresponding changelogs. |
|
any good ? |
phoneben
force-pushed
the
add-ami-event-filtering-docs
branch
2 times, most recently
from
d810e38 to
7dd1e4d
Compare
phoneben
force-pushed
the
add-ami-event-filtering-docs
branch
from
7dd1e4d to
cfceadf
Compare
Add comprehensive guide for Advanced Event Filtering Include syntax, examples, and best practices Document legacy filtering method with deprecation note Resolves asterisk#160
phoneben
force-pushed
the
add-ami-event-filtering-docs
branch
from
cfceadf to
cbaeae4
Compare
| | permit | ACL | An address/mask to allow in an ACL. This option may be present multiple times. | | | ||
| | acl | String | A Named ACL to apply to the client. | | | ||
| | setvar | String | A channel variable key/value pair (using the nomenclature VARIABLE=value) that will be set on all channels originated from this client | | | ||
| | eventfilter | RegEx | This option may be present multiple times. This options allows clients to whitelist or blacklist events. A filter is assumed to be a whitelist unless preceeded by a '\!'.Evaluation of the filters is as follows: |
There was a problem hiding this comment.
this should been removed should i open a separate pr for this mistake ?
There was a problem hiding this comment.
The past can not be altered, so a new PR would be needed regardless.
3 participants
Add comprehensive guide for Advanced Event Filtering Include syntax, examples, and best practices
Document legacy filtering method with deprecation note Resolves #160