[asterisk-bugs] [JIRA] (ASTERISK-27325) Asterisk Community Queue member stays “In Use” after parking a call

[Andres Miedzowicz (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-27325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andres Miedzowicz updated ASTERISK-27325:
-----------------------------------------

    Attachment: log.txt
                configuration.txt
                CLI Commands.txt

> Asterisk Community  Queue member stays “In Use” after parking a call
> --------------------------------------------------------------------
>
>                 Key: ASTERISK-27325
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27325
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_parkandannounce
>    Affects Versions: 13.17.0
>         Environment: OS: CentOS 6.7
> Kernel: 2.6.32-573.22.1.el6.x86_64
> Asterisk version: 13.17.0
> Hardware: Dell PE R200
>            Reporter: Andres Miedzowicz
>            Assignee: Unassigned
>         Attachments: CLI Commands.txt, configuration.txt, log.txt
>
>
> Call parking is configurated in Asterisk 13.17.0 (using PJSIP) using the default settings in res_parking.conf and features.conf. When a call enters a queue and the agent that picked up the call parks it, the status of that agent stays "In Use" until the call ends even though the agent is no longer involved in the call at all.
> For example, a call from Alice gets into a queue and gets answered by Bob. Bob parks the call and gets removed from the bridge. After that, Charlie picks up the parked call and talks to Alice normally. During this call, the status of Bob is "In Use" which doesn't allow him to get new calls. Only when the call between Alice and Charlie ends does Bob become available again.
> Example: Extension 681 calls the queue and it’s picked up by extension 687. The call is then parked by 687 and picked up by extension 689.
> My configuration is the following is in configuration.txt.
> The output of the CLI commands during each stage of the testing scenario is in cli commands.txt
> The log of the whole scenario can be found in log.txt



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