[asterisk-commits] file: trunk r89417 - in /trunk: ./ doc/tex/localchannel.tex

[SVN commits to the Asterisk project]

Author: file
Date: Mon Nov 19 09:27:08 2007
New Revision: 89417

URL: http://svn.digium.com/view/asterisk?view=rev&rev=89417
Log:
Merged revisions 89416 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r89416 | file | 2007-11-19 11:24:12 -0400 (Mon, 19 Nov 2007) | 4 lines

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:
    trunk/   (props changed)
    trunk/doc/tex/localchannel.tex

Propchange: trunk/
------------------------------------------------------------------------------
Binary property 'branch-1.4-merged' - no diff available.

Modified: trunk/doc/tex/localchannel.tex
URL: http://svn.digium.com/view/asterisk/trunk/doc/tex/localchannel.tex?view=diff&rev=89417&r1=89416&r2=89417
==============================================================================
--- trunk/doc/tex/localchannel.tex (original)
+++ trunk/doc/tex/localchannel.tex Mon Nov 19 09:27:08 2007
@@ -13,11 +13,11 @@
 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.
+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.
 
 There is another option that can be used with local channels, which is the "j"
 option.  The "j" option must be used with the "n" option to make sure that the