Search the Asterisk Blog

Asterisk 13.8.0 Highlights

By Kevin Harwell

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 just a few here. Namely, some of the new features that were added.

Registration context

The Asterisk pjsip channel driver now has a new option, regcontext. When specified a noop priority 1 extension is dynamically created for a configured endpoint upon registration. It is subsequently removed when the endpoint unregisters. The DUNDi protocol uses this feature to know that a particular peer contains an endpoint based on the fact that the extension exists.

To enable this feature within the Asterisk pjsip sub-sytem simply set the mentioned option in the global section of your ‘pjsip.conf’ file and give it a value that makes sense for your environment:

Full Backend Caching

Another feature newly included is a full backend caching strategy for the sorcery memory cache module. Previously the only option allowed was per-object caching. Now however, with full backend caching enabled all objects can be cached. This allows retrievals of all objects to be done against the cache itself without having to pull from the backend. This can be enabled by using the new full_backend_cache option within the sorcery.conf file. Within the configuration file, and for a specified modules object mappings, simply set the option on a type’s cache field. For instance, to turn on full caching for res_pjsip endpoints something similar to the following should be entered into the configuration file:

For more information and examples see the Asterisk wiki on on Sorcery Caching.

Bundled pjsip

Lastly another stand out feature is the inclusion of a bundled version pjsip within Asterisk. As this particular addition has been previously discussed see an Easier PJSIP Install Method for a detailed explanation.

Again these items are only some of the highlights. For a detailed list of all the changes that went into this release please see the ChangeLog-13.8.0 or the Changes file included with the Asterisk source code.

Download and try Asterisk 13.8.0 now!

There Are 3 Comments

  • Kyle says:

    Is it possible to create “real” (instead of noop) extension using regcontext?

    • Joshua Colp says:

      No, the functionality is simply there to activate a set of already existing dialplan logic by placing a first priority there. Having it do anything more would require a lot more configuration and complexity.

      • Kyle says:

        Could you elaborate more on “activate a set of already existing dialplan logic”? For instance if I have echo-test configured in dialplan – can I call an echo-test number from such dynamically created extension? Or maybe point to an example illustrating use of regcontext= option?

Add to the Discussion

Your email address will not be published. Required fields are marked *

About the Author

Kevin Harwell

Kevin is a Software Developer at Digium. He has a diverse background in the software industry and has worked on an assortment of projects. Since joining the Asterisk team a few years ago he has been a frequent contributor to a variety of areas within the project. He also can usually be seen with a cup of hot tea.

See All of Kevin's Articles

More From
The Digium Blog

  • No items