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 ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@89417 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
parent
9175f79aff
commit
a3ef17b4f2
|
@ -13,11 +13,11 @@ 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.
|
||||
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
|
||||
|
|
Loading…
Reference in New Issue