Files
asterisk/doc/apps.txt
Russell Bryant 1b8da31130 Making these documentation changes in the 1.4 branch upset various people, so
these chanes will only be done in the trunk.


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@58955 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2007-03-16 01:41:00 +00:00

11 lines
656 B
Plaintext

Asterisk applications register themselves with ast_application_register.
They should have a short, unique name, and an exec function which takes
as its arguments a channel and some data that might be useful for callback
stuff. Remember to keep track of how many and which channels are using
your application so that should the module need to be unloaded
(particularly force unloaded), you will be able to ast_softhangup all the
channels. An application should *never* call ast_hangup on the channel
that it is running on (although it could conceivably hang up other
channels that it allocates). See app_playback.c as an example of a simple
application.