diff options
| author | Terry Wilson <twilson@digium.com> | 2010-05-24 19:06:40 +0000 |
|---|---|---|
| committer | Terry Wilson <twilson@digium.com> | 2010-05-24 19:06:40 +0000 |
| commit | 3c9a8ebadb59ae5a906435c5767d85dae2d4f376 (patch) | |
| tree | 1b8fb2c3970ae1c3f0f408eaf13ca7c70c34a6a4 | |
| parent | 880cde12ac89b2d8a160416a9ff869befbd0d990 (diff) | |
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
| -rw-r--r-- | doc/tex/manager.tex | 17 |
1 files changed, 15 insertions, 2 deletions
diff --git a/doc/tex/manager.tex b/doc/tex/manager.tex index 6bf369040..7b7aff6d5 100644 --- a/doc/tex/manager.tex +++ b/doc/tex/manager.tex @@ -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} |