[asterisk-bugs] [JIRA] (ASTERISK-24630) Park extension created by 'parkext' option for custom parking lots only parks calls in the default lot

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224086#comment-224086 ] 

Rusty Newton commented on ASTERISK-24630:
-----------------------------------------

In the definitive guide I also found:

{quote}
To park a call in Asterisk, you need to transfer the caller to the feature code assigned to
parking, which is assigned in the features.conf file with the parkext directive. By default,
this is 700:
parkext => 700
; What extension to dial to park (all parking lots)
{quote}

Which still applies for the default lot.. but not for custom lots. So maybe something changed at some point and we didn't document it. 

> Park extension created by 'parkext' option for custom parking lots only parks calls in the default lot
> ------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24630
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24630
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Features/Parking, Resources/res_parking
>    Affects Versions: SVN, 11.15.0, 13.1.0
>         Environment: Affects both 11 (pre 12 parking changes) and Asterisk 13 (post changes)
>            Reporter: Rusty Newton
>            Severity: Minor
>
> For custom parking lots, the option {{parkext}} when populated results in the creation of a Park extension, but with no arguments, such that it only parks calls at the default lot.
> What is the point of the parkext option for custom lots?
> Asterisk 11
> {noformat}
> centosclean*CLI> dialplan show
> [ Context 'parkedcalls' created by 'features' ]
>   '700' =>          1. Park()                                     [features]
> [ Context 'mycustomlot' created by 'features' ]
>   '800' =>          1. Park()                                     [features]
> {noformat}
> Asterisk 13
> {noformat}
> [ Context 'mycustomlot' created by 'res_parking/mycustomlot' ]
>   '800' =>          1. Park()                                     [res_parking]
> <snip>
> [ Context 'parkedcalls' created by 'res_parking/default' ]
>   '700' =>          1. Park()                                     [res_parking]
> {noformat}
> An example Asterisk 13 configuration of res_parking.conf
> {noformat}
> [general]
> [mycustomlot]
> context => mycustomlot
> parkext => 800
> parkpos => 801-850
> {noformat}
> The same configuration works for features.conf in 11, but you need the {{parkinglot}} prefix for the custom lot.
> Dialing the created extension results in parking to the default lot.
> The workaround is of course dialing your own Park extension via other means and setting channel variables or application arguments to target the custom lot.
> It really feels like I'm missing something here. If not, then we should at a minimum document that the parkext option requires the setting of channel variables to access the custom parking lot.



--
This message was sent by Atlassian JIRA
(v6.2#6252)