A tale of Two Taskprocessors
Mike Bradeen
No Comments
Hi folks! Today, let’s take a look at a recent Asterisk issue: ASTERISK-29365. The graceful shutdown is intended to allow every part of the running
Hi folks! Today, let’s take a look at a recent Asterisk issue: ASTERISK-29365. The graceful shutdown is intended to allow every part of the running
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
Codec negotiation in Asterisk has been one of its deepest darkest secrets. It’s been around since the beginning and over the past two decades it’s
Within the Asterisk project we are constantly trying to improve our processes and data collection when a problem is encountered to reduce the back and
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.
Overview One of the most challenging things about coding is when your code doesn’t work and you have to figure out why. Trying to track
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
When the PJSIP work for Asterisk began one of the primary concerns kept in mind was that it be extensible. One of the APIs derived
Debugging SIP Messages the Traditional Way Since its release, the PJSIP stack has provided logging of SIP message traffic via the pjsip set logger CLI
