diff options
author | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-03-16 01:41:00 +0000 |
---|---|---|
committer | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-03-16 01:41:00 +0000 |
commit | dbddd24443348c19c79e9d85f40d2aa429d0d885 (patch) | |
tree | f88f0d9ea78ee8991946a97d9f7bfb720132ec4f /doc/model.txt | |
parent | b2830ad62612116f801a7ea10e8584a1bef42af0 (diff) |
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: http://svn.digium.com/svn/asterisk/branches/1.4@58955 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc/model.txt')
-rw-r--r-- | doc/model.txt | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/model.txt b/doc/model.txt new file mode 100644 index 000000000..10d2d0e05 --- /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 monitored 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 imminently be +terminated. + |