[asterisk-bugs] [JIRA] (ASTERISK-23943) Investigate configuration options to make extraneous Stasis messages optional

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-23943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan moved AFS-104 to ASTERISK-23943:
--------------------------------------------

    Asterisk Issue Guidelines: Yes.
                     Security: None  (was: Digium Only)
                   Regression: No
                     Workflow: Subtask and Courtesy Workflow  (was: Software Planning Workflow)
                          Key: ASTERISK-23943  (was: AFS-104)
                      Project: Asterisk  (was: Asterisk for SwitchVox (Internal))

> Investigate configuration options to make extraneous Stasis messages optional
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-23943
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23943
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>            Reporter: Matt Jordan
>            Assignee: Mark Michelson
>
> There are a fair number of Stasis messages (namely, those involving historical AMI events) that are a bit chatty. And silly.
> The two top candidates:
> # All AGI events
> # The dreaded RTCP events
> While filtering them from AMI "helps", it doesn't really solve the problem. When filtering is done via manager, it simply removes emitting the event - but it doesn't actually stop the querying/generation of channel snapshots.
> In general, it'd be much better if we could just eliminate the work in the first place.
> Starting with these two events, it would be worthwhile having configuration options (in rtp.conf and - unfortunately - a proposed agi.conf) to squelch generation of the messages completely. Default should be to emit them.



--
This message was sent by Atlassian JIRA
(v6.2#6252)