[asterisk-bugs] [Asterisk 0014882]: Parking extension number is not overriden in custom parking lots

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14882 
====================================================================== 
Reported By:                vmikhnevych
Assigned To:                mnick
====================================================================== 
Project:                    Asterisk
Issue ID:                   14882
Category:                   Channels/chan_features
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for review
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-04-13 04:07 CDT
Last Modified:              2010-05-10 11:12 CDT
====================================================================== 
Summary:                    Parking extension number is not overriden in custom
parking lots
Description: 
Example, from features.conf :
[general]
parkext => 700
.....

[PARKINGLOT_1]
parkext => 800
...

CLI command "features show" says that Parking extension is 700 for
PARKINGLOT_1

(Other options, like "Parking context" and "Parked call extensions" are
overriden correctly.)
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0014996 Multiple parking lots don't work
====================================================================== 

---------------------------------------------------------------------- 
 (0121649) lmadsen (administrator) - 2010-05-10 11:12
 https://issues.asterisk.org/view.php?id=14882#c121649 
---------------------------------------------------------------------- 
Is this fixed in 1.6.1.19 then? 1.6.2.7 and 1.6.1.19 were released at the
same time and any issues that affected both versions should have had it
included in both branches.

Any idea which issue or commit would have resolved it? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-10 11:12 lmadsen        Note Added: 0121649                          
======================================================================