diff options
author | markster <markster@f38db490-d61c-443f-a65b-d21fe96a405b> | 1999-10-08 04:46:33 +0000 |
---|---|---|
committer | markster <markster@f38db490-d61c-443f-a65b-d21fe96a405b> | 1999-10-08 04:46:33 +0000 |
commit | 795143ef36d7c9b43ff622e14c0b459ad25cb6a1 (patch) | |
tree | 16cb1647bbf3fbccde1e04de99acbc8ebdb0d713 /doc/model.txt | |
parent | 206fb36a6c314bd738d4e366edb580e5091870e4 (diff) |
Version 0.1.0 from FTP
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@2 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc/model.txt')
-rwxr-xr-x | doc/model.txt | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/model.txt b/doc/model.txt new file mode 100755 index 000000000..6afb3e04e --- /dev/null +++ b/doc/model.txt @@ -0,0 +1,15 @@ +Description of call model: + +Incoming Call: + + Channel backend waits for a RING or equivalent on some sort of +interface. Typically this is done in its own thread. When a RING is +detected, the backend should create a channel structure and then call +ast_pbx_start() on that channel, which will create a thread to monitor +that interface. At this point, the PBX and/or applications it launches +will manage the interface, and it need not be montored by the +aforementioned thread. When the applications are finished, the requisite +hangup function will be called, at which the channel can be considered to +be no longer valid, and the thread that controls it will immenantly be +terminated. + |