Add the FullyBooted AMI event

It is possible to connect to the manager interface before all Asterisk modules
are loaded. To ensure that an application does not send AMI actions that might
require a module that has not yet loaded, the application can listen for the
FullyBooted manager event. It will be sent upon connection if all modules have
been loaded, or as soon as loading is complete. The event:

   Event: FullyBooted
   Privilege: system,all
   Status: Fully Booted

Review: https://reviewboard.asterisk.org/r/639/


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@265320 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Terry Wilson 2010-05-24 19:06:40 +00:00
parent 880cde12ac
commit 3c9a8ebadb
1 changed files with 15 additions and 2 deletions

View File

@ -28,8 +28,6 @@ If you develop applications, please try to reuse existing manager
headers and their interpretation. If you are unsure, discuss on
the asterisk-dev mailing list.
\section{Device status reports}
Manager subscribes to extension status reports from all channels,
to be able to generate events when an extension or device changes
state. The level of details in these events may depend on the channel
@ -111,6 +109,21 @@ There are a number of GUI tools that use the manager interface, please search
the mailing list archives and the documentation page on the
\url{http://www.asterisk.org} web site for more information.
\section{Ensuring all modules are loaded}
It is possible to connect to the manager interface before all Asterisk modules
are loaded. To ensure that an application does not send AMI actions that might
require a module that has not yet loaded, the application can listen for the
FullyBooted manager event. It will be sent upon connection if all modules have
been loaded, or as soon as loading is complete. The event:
\begin{verbatim}
Event: FullyBooted
Privilege: system,all
Status: Fully Booted
\end{verbatim}
\section{Device status reports}
\section{Some standard AMI headers}
\begin{verbatim}