diff options
| author | twilson <twilson@f38db490-d61c-443f-a65b-d21fe96a405b> | 2010-05-25 13:33:21 +0000 |
|---|---|---|
| committer | twilson <twilson@f38db490-d61c-443f-a65b-d21fe96a405b> | 2010-05-25 13:33:21 +0000 |
| commit | aae81a7692e119801f67d949f3e34fe8300ae1a3 (patch) | |
| tree | b9fd993977d92551b14b76631ed602cc64afb126 /doc | |
| parent | c0a9e37b403684e00f0095efe8ca3bbc46e0ea55 (diff) | |
Merged revisions 265320,265467 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk
........
r265320 | twilson | 2010-05-24 14:06:40 -0500 (Mon, 24 May 2010) | 14 lines
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/
........
r265467 | twilson | 2010-05-24 17:21:58 -0500 (Mon, 24 May 2010) | 1 line
Merge the rest of the FullyBooted patch
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@265570 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manager.txt | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/manager.txt b/doc/manager.txt index a0a832c8d..b6cc6f35b 100644 --- a/doc/manager.txt +++ b/doc/manager.txt @@ -122,6 +122,23 @@ Parameters: Channel, Timeout You can always get more information about a manager command with the "show manager command <command>" CLI command in Asterisk. +Determining when all modules have finished loading +-------------------------------------------------- +It is handy to have a single event notification for when all Asterisk +modules have been loaded--especially for situations like running +automated tests. This event will fire 1) immediately upon all modules +loading or 2) upon connection to the AMI interface if the modules have +already finished loading before the connection was made. This ensures +that a user will never miss getting a FullyBooted event. In vary rare +circumstances, it might be possible to get two copies of the message +if the AMI connection is made right as the modules finish loading. + +Example: + Event: FullyBooted + Privilege: system,all + Status: Fully Booted + + Examples -------- Login - Log a user into the manager interface. |