PJSIP Transport Reload Changes
Joshua C. Colp
No Comments
In a past blog post I talked about how you can’t reload transports without enabling explicit support, but alluded to changes coming in the future.
In a past blog post I talked about how you can’t reload transports without enabling explicit support, but alluded to changes coming in the future.
When PJSIP support in Asterisk was being developed one of the critical areas of development was transports. These are for the most part provided by
In the past month I’ve been fixing an issue with Asterisk and PJSIP that I thought would be fun to share in a blog post.
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,
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
What is STIR/SHAKEN? STIR/SHAKEN (Secure Telephony Identity Revisited / Signature-based Handling of Asserted information using toKENs) is a new technology that the telecommunications industry is
When transitioning from the chan_sip channel driver to chan_pjsip one of the items that can catch people off guard is the use of SIP URIs
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
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
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
