Joshua C. Colp

Greetings Everyone! Time flies when you are having fun and improving Asterisk; this past year has been no different. October and Astricon [1] are fast approaching; and, thus, the first

A comment that I see frequently when helping people with PJSIP is the lack of a general section (with global options) and how this causes their configuration to be larger

When DTLS support in Asterisk was added the information about how to use DTLS support in OpenSSL was not as flushed out as it is today. To that end the

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 happening in Asterisk and to

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 and a mechanism to set

In Asterisk we have an API called device state. As the name implies this allows a device (such as a PJSIP endpoint) to provide notification to the system of its

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 implementation for it. When these

The stasis message bus is something that is used every day as of Asterisk 13 when you are using Asterisk. It provides the foundation of such things as CDR, CEL,

In the past, we’ve had a few blog posts talking about specific parts of new WebRTC work that has been done in Asterisk; but, with the release of Asterisk 16,

One of the most difficult things in PJSIP is ensuring that the experience is the best it can be for not just people who configure their Asterisk from normal configuration