Video has been a continued theme of Asterisk for some years now. We put into place the foundation to allow us to do video better, and have over time taken advantage of this and advanced things further. I thought I would take a little bit of time to reflect back on what has been done.
Greetings Everyone! Another year has flown by and while we now live in interesting times this has not stopped the development and progress of Asterisk or the Astricon conference[1], so much so that the first release candidate of Asterisk 18 is here[2]. The first step in creating the 18.0.0 release of Asterisk is tagging a
When stream support was initially added to Asterisk we did it in the most backwards compatible way possible to ensure that we did not have to modify the entirety of Asterisk. This has allowed us to gradually improve parts of Asterisk as we’ve expanded our stream and video support. To that end the next part
In a blog post long ago we talked about the addition of the create and dial ARI functionality for allowing channels to exist within ARI applications before they have been answered. This has seen use by various people and it came to light that it presented a slight difference in API definition in comparison to
In a blog post long ago we talked about the addition of the create and dial ARI functionality for allowing channels to exist within ARI applications before they have been answered. This has seen use by various people and it came to light that it presented a slight difference in API definition in comparison to
When PJSIP support was written for Asterisk we naturally needed the ability to display the SIP messages being sent and received. This took the form of the res_pjsip_logger module which hooks into the message sending and receiving path and logs the messages. The functionality was written to be familiar to users of chan_sip by allowing
The ConfBridge dialplan application is used countless times each day by people to do conferencing. Long ago this was done using the MeetMe dialplan application that utilized DAHDI functionality but with the requirement on DAHDI for it to operate an alternative was needed and ConfBridge came into existence. Have you ever wondered how it actually
Review If you’ve been following this blog post series, then you should have a channel driver that’s ready to be integrated with ARI. If not, then check out Part 1 and Part 2 first. The purpose of this final chapter in the series will be to get your channel driver working with ARI, which is
When stream support was added to Asterisk it was initially done with the focus being for SFU with a single video stream from each participant with the call starting out with video. This is a use case which is useful for a lot of people and has worked well. Coming soon, however, is the ability
When PJSIP publish and subscribe functionality was created we knew we wanted to provide a pluggable mechanism to allow modules to easily extend and add new bodies. The result of this is what is known as body generators. Given a set of data they convert it into a format expected by a device, such as
