From b9c82e8f661222ca33115188c776735e4c2bd8c3 Mon Sep 17 00:00:00 2001 From: file Date: Thu, 29 Oct 2009 18:11:26 +0000 Subject: Add an option to enabling passing music on hold start and stop requests through instead of acting on them in chan_local. (closes issue #14709) Reported by: dimas git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@226531 f38db490-d61c-443f-a65b-d21fe96a405b --- doc/localchannel.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/localchannel.txt b/doc/localchannel.txt index ccedbebed..33b9fbc2f 100644 --- a/doc/localchannel.txt +++ b/doc/localchannel.txt @@ -5,10 +5,12 @@ chan_local is a pseudo-channel. Use of this channel simply loops calls back into * Syntax: - Local/extension@context[/n] + Local/extension@context[/nm] 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. +Adding "/m" at the end will cause chan_local to forward music on hold start and stop requests. Normally chan_local acts on them and it is started or stopped on the Local channel itself. + * Purpose: The Local channel construct can be used to establish dialing into any part of the dialplan. -- cgit v1.2.3