Blog Author
Logging in software is usually a good thing. It’s often used to output useful information and/or statistics relevant to a current software task. However, everything comes with a cost, and logging is no exception. Excessive logging slows a system down. As well “information overload” can actually confuse a situation and complicate things. Like any good
We’ve had a few questions about whether or not Asterisk could easily install on CentOS 8. A few months ago the answer to that question was no. However, given some time, a few added packages later, and a custom open source repository contribution we now believe that answer has changed. In this post I’ll explain
A past post discusses some tips and tricks to employ when encountering a problem. Here we’ll walk through an issue applying some of those techniques. Recently an Asterisk issue came up involving occasional static and/or silence for audio. Broadly speaking the problem can be described as Alice calls Bob (using SIP), Bob answers, the call
The Asterisk Rest Interface (ARI) over the last year received several enhancements that have been requested by the community: server side event filtering automatic context creation moving a channel between apps Although these topics have been discussed previously, with Astricon, and the release of Asterisk 17.0.0 just around the corner I think it’s a good
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 has been created to help address some of the complications that arise when attempting to store, and administer state within stasis. Stasis Cache and Topic Pool Typically, the stasis cache
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 Asterisk. Background Many moons ago REMB support was added to Asterisk. In order to support a large bit rate the REMB RFC represents the value as mantissa and exponent. Both
Since the arrival of the Asterisk REST Interface (ARI) requests have been made to allow for event type filtering capabilities. Consumers have wanted a way to make it so Asterisk only sends a specified subset of events to the connected application. Guess what, the wait is finally over! Starting with Asterisk 13.26.0, and Asterisk 16.3.0
Measuring performance in Asterisk, like most software systems for that matter, can be a complicated task. When testing performance it is important to define goals, and limit the context for that which is being tested. It’s been previously shown that res_pjsip might have an efficiency problem when it comes to inbound registration. Our main goal for this
Let’s talk some more about testing, understanding the test framework for Asterisk, and building better tests. An exciting topic I know! In a previous post, we discussed how unit testing Asterisk worked. Here, though we’ll be talking a bit about the Asterisk Test Suite. The Asterisk Test Suite is a way to write automated, functional, “black-box”
Asterisk allows users to manipulate call party identification information through mechanisms like configuration options and dialplan functions (for instance CALLERID and CONNECTEDLINE to name a couple). This grants the user freedom to adjust values with regards to what call/caller information to expose and/or override. With this freedom, though, comes some complexity, and confusion. Especially when
