It seems just like yesterday that Asterisk 13.8.0 was released but here we are with an Asterisk 13.9.0 (and subsequently 13.9.1). This post shines the light on some notable changes that may impact and be useful for everyone. app_queue A change went in to Asterisk 13.8.0 to fix an issue where the wrapuptime would not
Been wanting to try the new PJSIP stack but finding the configuration a little daunting? Then this blog post is for you! While the basic PJSIP configuration objects (endpoint, aor, etc.) allow a great deal of flexibility and control they can also make configuring standard scenarios like ‘trunk’ and ‘user’ more complicated than similar sip.conf scenarios. The
The PJSIP library now used by Asterisk to provide SIP support has included basic SIP DNS support for quite some time. However through using it ourselves and from feedback from the community we determined that it was not as feature rich as we would like and as part of Asterisk 14 we set about improving
Asterisk 13.8.0 was just recently released. As usual this release includes bug fixes as well as a few new features. Many of which were submitted and patched by community members and contributors. Many thanks goes out to all those who made this release a success. As mentioned many items were attended to, but we’ll highlight
What is call parking? Call parking is a means of placing a call on hold so anyone can retrieve the call if they know where the call is parked. The natural metaphor to describe how the feature operates is a car parking lot. In fact many of the call parking options use car parking terminology
When you file an issue on the Asterisk JIRA you might notice that a few people may end up looking and participating in it. The first person, however, is usually just doing triage. What is triage? Well – before a developer looks at an issue it is vetted to ensure that it is a valid issue
Asterisk 13.8.0 will come with a new option for enabling PJSIP functionality. This functionality is called bundling and comes courtesy of a community member, George Joseph, who you can also thank for such PJSIP additions as wizards for configuration and the PJSIP_HEADER dialplan function. Before we talk about bundling let’s take a look at the history
Veterans of Asterisk configuration have likely dealt with static configuration files or realtime before. Since Asterisk 13.5.0, there is a new player in town: ARI push configuration. How does ARI push configuration work? ARI push configuration uses a subsystem of Asterisk called sorcery. This is the first mention of sorcery on this blog, and I
So you’ve written some code for Asterisk and now you need to test it. The Asterisk project has support for both integration and unit testing. In this post we’ll talk about the latter, how to write a unit test. Luckily, for someone already modifying, or adding to, the Asterisk source writing a unit test has
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 command. This dumps all received and transmitted SIP messages as a VERBOSE message. This is useful for two scenarios: When wanting to log all SIP messages in an Asterisk log
