[asterisk-bugs] [Asterisk 0012399]: variables utilized with Dial command and parameter L, appear to be neglected when utilizing a chan_local combo

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12399 
====================================================================== 
Reported By:                greenfieldtech
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12399
Category:                   Channels/chan_local
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-09-2008 16:31 CDT
Last Modified:              04-10-2008 17:42 CDT
====================================================================== 
Summary:                    variables utilized with Dial command and parameter
L, appear to be neglected when utilizing a chan_local combo
Description: 
Ok, this is a little complex, so please bear with me for the explanation:

I have a script operating with the AMI, simply originating calls to
chan_local, and then once chan_local picks up, they will connect the calls
to an extension. Up till now, this is very simple. The call is originated
to the callback_dummy context, using the combo
Local/1234567890 at callback_dummy

Once the call to the extension had been picked up by Asterisk, the
dialplan directs the extension to dial to an outbound number, using the
call_originator context, which appears in the Exten/Context part of the
originate request.

Once the target "originator" had been contacted, Asterisk will then
transfer both channels in to the call_target_dummy context, hanging up the
local channel, and directing the "real" channel in to the call_target
context. Once in call_target, Asterisk would then dial the "target" number.


As you can see in the dial plan below, I've defined the L parameter, in
order to limit the duration of the call. The funny part of this is that
while the call time is being limited correctly, the warning sounds that are
supposed to be played, are not played - to any of the parties.

I was under the impression that this is a chan_local issue, or something
that can't be done. However, after consulting punopvut@#asterisk-bugs, he
indicated that a bug should be opened. 

The following may also shed some light here, I've also tried replacing the
dialing at call_target to a backgroundDetect, and it would appear as if
Asterisk isn't even aware that an RTP stream is available for background
detection.

* I've marked the severity on this as "major", as I'm currently in the
process
  of developing an application that require heavy usage of chan_local, and
it 
  would appear that it may cause issues.

* If additional information is required, please direct me to what needs to
be   
  done in order to gather the information, and I'll post it.

====================================================================== 

---------------------------------------------------------------------- 
 greenfieldtech - 04-10-08 17:42  
---------------------------------------------------------------------- 
Please close this issue, this is was a dialplan issue - not a bug. 
Sorry for the mistake. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-10-08 17:42  greenfieldtech Note Added: 0085326                          
======================================================================