[asterisk-bugs] [Asterisk 0016527]: Verbose for Call Parking is incorrect

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16527 
====================================================================== 
Reported By:                journo
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16527
Category:                   Applications/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-30 09:26 CST
Last Modified:              2011-01-28 11:39 CST
====================================================================== 
Summary:                    Verbose for Call Parking is incorrect
Description: 
When you park a call, the verbose provided is incorrect. At the time of
parking, it reports that its going to timeout to the extension that the
caller originally dials, rather than the extention that is parking the
call.
====================================================================== 

---------------------------------------------------------------------- 
 (0131180) davidw (reporter) - 2011-01-28 11:39
 https://issues.asterisk.org/view.php?id=16527#c131180 
---------------------------------------------------------------------- 
This is not as simple as it seems.  This code can be used in environments
where the message will be true, at least on 1.6.x.

The situation can arise explicitly, but can also arise if the second
channel on an AMI park is one of those being closed out by the masquerade
in masq_park_call, at least when a Local channel is involved.  What seems
to happen is that asterisk tries to find the owner side of the local
channel, then its bridged peer, and finally that's name.  If the local
channel is anywhere in the call chain that is being closed because the
original channel that was parked has become a zombie, I suspect it ends up
accessing the name of a channel that has already been deleted.

With current 1.6 versions, specifying an explicit destination will also
override the return channel.

One other technicality to note is that the behaviour in the simple case is
to return to the device associated with the channel that parked the call. 
It does not return to an extension, and that device might not even have an
extension configured (the parking timeout logic creates a temporary
extension, referring to the device, at the time of the timeout, put that
extension doesn't look like a normal extension).  It might also have
multiple extensions referencing it.

I did try to raise a question on the developer list, at the end of the
last, week, which covered some of this, but all my postings to the
developer list and its owner seem to be disappearing. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-28 11:39 davidw         Note Added: 0131180                          
======================================================================