[asterisk-bugs] [JIRA] (ASTERISK-22800) Dynamic parking pickup doesn't use PARKINGLOT

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-22800:
--------------------------------------------

Asterisk has always deleted the generated ParkedCall() exten when a call is picked up so you would have a different problem anyway.  The first call would get picked up but the second call could not be picked up because the exten no longer exists.

Overlapping parking lots are possible if you do *not* use the automatically generated extensions.

{noformat}
[my_park]
; This application must be used as the first extension priority
; to be recognized as a parking access extension.  DTMF transfers
; and some channel drivers need this distinction to operate properly.
; The parking access extension in this case is treated like a dialplan
; hint because the Park application does not get executed.
exten => 700,1,Park()

exten => _7XX,1,ParkedCall(${EXTEN})
{noformat}
                
> Dynamic parking pickup doesn't use PARKINGLOT
> ---------------------------------------------
>
>                 Key: ASTERISK-22800
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22800
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Features/Parking
>    Affects Versions: 1.8.12.2
>         Environment: CentOS release 5.8 64 bit
>            Reporter: David Cunningham
>            Assignee: Richard Mudgett
>         Attachments: park1.log.gz
>
>
> When picking up a call from a dynamically created parking lot, specified with the PARKINGLOT variable, the wrong call is picked up.
> A full trace is attached. The call flow is:
> 1. External caller 0000101 called 0234567890 which routed to telephone 2000105.
> 2. Telephone 2000105 parked the call using #*7 on lot park_4, slot 701.
> 3. Telephone 1000102 called 1000101.
> 4. Telephone 1000101 parked the call using #*7 on lot park_3, slot 701.
> 5. Telephone 2000105 dialled 701 and got the call parked at step 4, which is the wrong one.
> The important part of the trace is:
> {noformat}
> [Nov  1 11:49:44] VERBOSE[2694] res_agi.c: <SIP/product-local-00000069>AGI Rx << VERBOSE "Picking up call parked in 701" 9
> [Nov  1 11:49:44] VERBOSE[2694] res_agi.c: <SIP/product-local-00000069>AGI Tx >> 200 result=1
> [Nov  1 11:49:44] VERBOSE[2694] res_agi.c: <SIP/product-local-00000069>AGI Rx << SET VARIABLE __PARKINGLOT "park_4"
> [Nov  1 11:49:44] VERBOSE[2694] res_agi.c: <SIP/product-local-00000069>AGI Tx >> 200 result=1
> and then:
> [Nov  1 11:49:44] DEBUG[2698] pbx.c: Launching 'ParkedCall'
> [Nov  1 11:49:44] DEBUG[2698] features.c: Found Parking lot: park_3
> {noformat}
> For some reason it's using park_3, when it should be using park_4 as specified in PARKINGLOT.
> The output of "parkedcalls show" while both calls were parked was:
> {noformat}
> Num        Channel                   (Context         Extension     Pri) Timeout
> *** Parking lot: park_4 (1)
> 701        Local/*7 at parkedcalls-9d2a;2 (parkedcalls     s               1)     40s
>    1 parked call in parking lot park_4
> *** Parking lot: park_3 (1)
> 701        Local/*7 at parkedcalls-9b7c;2 (parkedcalls     s               1)     54s
>    1 parked call in parking lot park_3
> *** Parking lot: default (0)
> ---
> 2 parked calls in total.
> {noformat}
> And after the pickup was the following, which shows the wrong call was picked up:
> {noformat}
> Num        Channel                   (Context         Extension     Pri) Timeout
> *** Parking lot: park_4 (1)
> 701        Local/*7 at parkedcalls-9d2a;2 (parkedcalls     s               1)     24s
>    1 parked call in parking lot park_4
> *** Parking lot: park_3 (1)
> *** Parking lot: default (0)
> ---
> 1 parked call in total.
> {noformat}
> Thank you.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira