A note about qualified endpoints and DNS
Mike Bradeen
No Comments
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
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
Asterisk 18.17.0 and 20.2.0 were released recently with support for PJSIP 2.13. This version of PJSIP includes an important change to deal with race conditions
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
Overview Everyone knows that PJSIP is the channel driver of choice for Asterisk nowadays. It’s a powerful driver, but that doesn’t mean there isn’t more
Recently I spent some time updating Asterisk to the latest versions of the third party libraries we bundle. This includes jansson as well as PJSIP,
STIR/SHAKEN in 2021 It’s been a while since the release of Asterisk 18 and the STIR/SHAKEN update. During this time, we’ve discovered that the specification
An interesting issue was recently filed where dialing a Local channel resulted in the following: [2021-03-28 22:41:35] ERROR[15773][C-00000030]: translate.c:1396 ast_translator_best_choice: Cannot determine best translation path
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.
