Stasis State: Improved Management
Kevin Harwell
2 Comments
Stasis has been a core part of Asterisk for a while now. However, state management within it is a bit precarious. A new stasis_state module
Stasis has been a core part of Asterisk for a while now. However, state management within it is a bit precarious. A new stasis_state module
Manager is an API that has been in Asterisk for almost as long as Asterisk has existed. It provides a mechanism to see what is
I’ve previously written about REMB, or receiver estimated maximum bitrate, and its effect on video quality. While this provides periodic feedback from receivers to Asterisk
Back in December in my The Continuing Saga of Continuous Integration blog post I wrote about how we reduced the Testsuite’s “27” layers of file
Overview For those of you who have been around for a while now and contribute to the code base, you probably know about CHANGES and
I ran into a curious problem the other day while working on an issue involving the storage, manipulation, and conversion of large number values in
Overview One of the topics of discussion every year at Astricon is not needing to use the dialplan in order to use Stasis. This involves
Asterisk developers who have made use of one of our function attributes called “force_inline” should be aware we are discouraging it. Why? Let’s get to
Previously on this blog I talked about a new feature to internally filter messages in our internal message bus, as well as a new caching
or… “Watch This Space” If you’re an Asterisk contributor you’ve probably noticed that we’d been having issues with large numbers of Jenkins test failures during
