[asterisk-bugs] [Asterisk 0013494]: One-touch parking failure results in the call drop, while parties should be able to continue conversation

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13494 
====================================================================== 
Reported By:                mdu113
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   13494
Category:                   Resources/res_features
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 142474 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-16 11:45 CDT
Last Modified:              2009-01-23 10:24 CST
====================================================================== 
Summary:                    One-touch parking failure results in the call drop,
while parties should be able to continue conversation
Description: 
I believe that in case of one-touch parking, a parking failure should not
cause the call to be dropped.
Scenario: A calls B, B answers and attempts to park A. If the parking
fails for any reason (requested parking extension is busy or all parking
spaces are already in use) then asterisk now drops the call, while I
believe the parties should be able to continue conversation and possibly
make another parking attempt later.
====================================================================== 

---------------------------------------------------------------------- 
 (0098572) jpeeler (administrator) - 2009-01-23 10:24
 http://bugs.digium.com/view.php?id=13494#c98572 
---------------------------------------------------------------------- 
After discussing this the current defined behavior is unexpected so I'm
going to start working on this. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-23 10:24 jpeeler        Note Added: 0098572                          
======================================================================