aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorfile <file@f38db490-d61c-443f-a65b-d21fe96a405b>2007-11-19 15:24:12 +0000
committerfile <file@f38db490-d61c-443f-a65b-d21fe96a405b>2007-11-19 15:24:12 +0000
commit8e311576e0c99395ead07f1a17a420b202b56e84 (patch)
tree23055a32724d33ece6d0eae52d90839df092e0e8 /doc
parentd95d9bb24ea20a2859f16b74d93d4379466983df (diff)
Clarify documentation a bit, include that a frame has to pass through the core in order for the Local channel optimization to happen.
(closes issue #11246) Reported by: jon git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@89416 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc')
-rw-r--r--doc/localchannel.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/localchannel.txt b/doc/localchannel.txt
index f96ea15ec..ccedbebed 100644
--- a/doc/localchannel.txt
+++ b/doc/localchannel.txt
@@ -7,7 +7,7 @@ chan_local is a pseudo-channel. Use of this channel simply loops calls back into
Local/extension@context[/n]
-Adding "/n" at the end of the string will make the Local channel not do a native transfer (the "n" stands for "n"o release) upon the remote end answering the line. This is an esoteric, but important feature if you expect the Local channel to handle calls exactly like a normal channel. If you do not have the "no release" feature set, then as soon as the destination (inside of the Local channel) answers the line, the variables and dial plan will revert back to that of the original call, and the Local channel will become a zombie and be removed from the active channels list. This is desirable in some circumstances, but can result in unexpected dialplan behavior if you are doing fancy things with variables in your call handling.
+Adding "/n" at the end of the string will make the Local channel not do a native transfer (the "n" stands for "n"o release) upon the remote end answering the line. This is an esoteric, but important feature if you expect the Local channel to handle calls exactly like a normal channel. If you do not have the "no release" feature set, then as soon as the destination (inside of the Local channel) answers the line and one audio frame passes, the variables and dial plan will revert back to that of the original call, and the Local channel will become a zombie and be removed from the active channels list. This is desirable in some circumstances, but can result in unexpected dialplan behavior if you are doing fancy things with variables in your call handling.
* Purpose: