If you didn’t already know, both SIP and HTTP share the same digest authentication mechanism described all the way back in RFC-2069 “An Extension to HTTP
As mentioned in this post, Asterisk now supports the use of RFC4733 digits in common bitrates beyond 8kHz. At the end of the post, we
The ability to send SIP NOTIFY messages to endpoints and arbitrary uri’s via AMI and CLI has existed for some time within Asterisk. Changes from
In a previous blog post we talked about using Asterisk’s uni-cast functionality as a bridge between the PSTN and an external service. This post entails
A recurring theme I’m seeing lately is people deploying VoIP, running into issues, and not approaching their issues from the perspective of taking all components
Note: This new implementation is available as of Asterisk 18.22.0, 20.7.0, and 21.2.0. It’s been almost 4 years since STIR/SHAKEN support was first added to
Most SIP endpoints will qualify each other by sending OPTIONS back and forth to make sure they are there and can respond. Asterisk uses this mechanism
This is a bit of a strange blog post but recent responses to people reminded me of the Colp Hard Facts webinar I did recently.
I help out a lot across various avenues: mailing lists, forums, issue tracker, IRC, and more. I’ve noticed a trend recently where people aren’t verifying
Asterisk 21 is scheduled to become the next major release. As part of that process there are a number of modules being removed, see: wiki.asterisk.org.
The Sangoma Blog