Review Board 1.7.16

Rework the Asterisk indications API

Review Request #149 - Created Feb. 10, 2009 and submitted

Russell Bryant
This patch includes a number of changes to the indications API.  The primary motivation for this work was to improve stability.  The object management in this API was significantly flawed, and a number of trivial situations could cause crashes.

The changes included are:

1) Remove the module res_indications.  This included the critical functionality that actually loaded the indications configuration.  I have seen many people have Asterisk problems because they accidentally did not have an indications.conf present and loaded.  In fact, this came up again in #asterisk-dev today.  Now, this code is in the core, and Asterisk will fail to start without indications configuration.  

There was one part of res_indications, the dialplan applications, which did belong in a module, and have been moved to a new module, app_playtones.

2) Object management has been significantly changed.  Tone zones are now managed using astobj2, and it is no longer possible to crash Asterisk by issuing a reload while tone zones are in use.

3) The API documentation has been filled out.

4) The API has been updated to follow our naming conventions.

5) Various bits of code throughout the tree have been updated to account for the API update.

6) Configuration parsing has been mostly re-written.

7) "Code cleanup"
Basic testing playing different tones using the Playtones() application works fine.
Review request changed
Updated (Feb. 16, 2009, 5:58 a.m.)
Remove a trailing space.  There are now no trailing whitespace problems in this patch.  :-)
Ship it!
Posted (Feb. 17, 2009, 8:09 a.m.)
 runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA.
Please report problems with this site to