[asterisk-bugs] [JIRA] (ASTERISK-28072) app_agent_pool: Crash when heavily manipulated externally using AMI

Joshua C. Colp (JIRA) noreply at issues.asterisk.org
Wed Oct 17 14:52:47 CDT 2018


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

Joshua C. Colp commented on ASTERISK-28072:
-------------------------------------------

You can provide more examples to help when someone looks at this. There is no time frame on that, though.

> app_agent_pool: Crash when heavily manipulated externally using AMI
> -------------------------------------------------------------------
>
>                 Key: ASTERISK-28072
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28072
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_agent_pool
>    Affects Versions: 13.20.0, 13.23.0
>         Environment: CentOS 6
>            Reporter: Jeff Hoppe
>            Assignee: Unassigned
>            Severity: Minor
>         Attachments: Agent Functionality.pdf, backtrace0925.txt, backtrace1002.txt, Crash Case #3.pdf, Full Log for Thead 15274.txt, xaa.gz, xab.gz, xac.gz, xad.gz, xae.gz, xaf.gz, xag.gz, xah.gz
>
>
> When an agent leaves the app pool to join a conference call they need to be re-logged in to the app pool when done.   I use AMI to redirect the agent channel to this context:
> {noformat}
> ; ------ when agent leaves the realm they will call this to get back in.
> [agentrelogin]
> exten => 11,1,NoOp()
> exten => 11,n,AgentLogin(${agentid},s)
> {noformat}
> Occasionally we get an Asterisk crash as specified in the attached log.



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



More information about the asterisk-bugs mailing list