| Summary: | ASTERISK-23943: Investigate configuration options to make extraneous Stasis messages optional | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | |
| Date Opened: | 2014-06-25 18:53:30 | Date Closed: | 2014-08-06 08:08:44 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Resources/res_ari |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | 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. | ||
| Comments: | By: Kinsey Moore (kmoore) 2014-08-06 08:08:44.473-0500 Committed to trunk. | ||