[asterisk-commits] file: branch 1.4 r89416 - /branches/1.4/doc/localchannel.txt

[SVN commits to the Asterisk project]

Author: file
Date: Mon Nov 19 09:24:12 2007
New Revision: 89416

URL: http://svn.digium.com/view/asterisk?view=rev&rev=89416
Log:
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

Modified:
    branches/1.4/doc/localchannel.txt

Modified: branches/1.4/doc/localchannel.txt
URL: http://svn.digium.com/view/asterisk/branches/1.4/doc/localchannel.txt?view=diff&rev=89416&r1=89415&r2=89416
==============================================================================
--- branches/1.4/doc/localchannel.txt (original)
+++ branches/1.4/doc/localchannel.txt Mon Nov 19 09:24:12 2007
@@ -7,7 +7,7 @@
 
  Local/extension at 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: