...

• The hook that the plugin module should be called by (effectively what subclass of 'Plugin' it is); shown in red.
• The name of the plugin instance (it is possible to configure more than one copy of the same plugin with different names, each with its configuration values); shown in blue
• The shared library that implements the plugin; shown in green
• Any configuration name/value pairs required by the plugin; shown in orange

Configuration File Names and Structure

The Old Way

In 4.2 and earlier, all plugins for a component were configured by adding lines to the (single) *-config file for the component; in the case of the registrar, this is /etc/sipxpbx/registrar-config

...

The New Way

In 4.3 each hook for a component has a directory into which a separate configuration file is written for each plugin instance. So, for the registrar, which has two different plugin hooks, there will be two directories:

...

List of Plugins

TBD