This post on the Digium blog represents the first in a new series, “Developing in Asterisk”, focusing on (of all things) Asterisk development. The topics will explore building things inside and on top of Asterisk – everything from core Asterisk development to building external applications utilizing Asterisk interfaces. Since Asterisk is a continually evolving project, these blog posts will link to content on the Asterisk wiki. That way, as things change, the content can change along with it!
As the first installment in this series, here is an overview of using the new Configuration Framework for Asterisk modules in Asterisk 11. This Wiki article looks at common pitfalls in extracting configuration information from static Asterisk configuration files and how the new Configuration Framework alleviates those problems. Using the new Configuration Framework in your module helps to ensure that module loading in Asterisk is done in a thread-safe, consistent manner.
“Modules in Asterisk – be they applications, functions, channel drivers, supplementary resources, etc. – are responsible for managing their own resources and responding to operations initiated by the Asterisk core. During module load and reload operations, a large part of this responsibility consists of loading and parsing the module’s configuration information from an Asterisk compatible configuration file or, optionally…”
Want to Continue Reading?
Visit the Asterisk wiki to learn more about How to Use the Configuration Framework!