Module of FreePBX (Custom Applications) :: Registry to add custom extensions and destinations that may be created and used so that the Extensions and Destinations Registry can include these.

Creates custom contexts which can be used to allow limited access to dialplan applications. Allows for time restrictions on any dialplan access. Allows for pattern matching to allow/deny. Allows for failover destinations, and PIN protected failover. This can be very useful for multi-tennant systems. Inbound routing can be done using DID or zap channel routing, this module allows for selective outbound routing. House/public phones can be placed in a restricted context allowing them only internal calls

Module of FreePBX (System Dashboard) :: Provides a system information dashboard, showing information about Calls, CPU, Memory, Disks, Network, and processes.

Call Flow manual toggle control - allows for two destinations to be chosen and provides a feature code that toggles between the two destinations.

This uses the app_dictate module of Asterisk to let users record dictate into their phones. When complete, the dictations can be emailed to an email address specified in the extension page

FreePBX "directory" module

DISA Allows you 'Direct Inward System Access'. This gives you the ability to have an option on an IVR that gives you a dial tone, and you're able to dial out from the FreePBX machine as if you were connected to a standard extension. It appears as a Destination.

Provides donotdisturb featurecodes

This module will check all configured and enabled DUNDi trunks as part of the extension registry function, and report back conflicts if other sites have the same extensions. This does not filter against the route patterns - it will take any number being created and report a conflict if that trunk could be used to call that number.