[asterisk-bugs] [JIRA] (ASTERISK-28072) AgentLogin application is crashing

[Jeff Hoppe (JIRA)]

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

Jeff Hoppe updated ASTERISK-28072:
----------------------------------

    Attachment: xah.gz
                xag.gz
                xaf.gz
                xae.gz
                xad.gz
                xac.gz
                xab.gz
                xaa.gz
                Crash Case #3.pdf
                backtrace1002.txt

Here is the back trace (backtrace1002.txt) for a crash.  
Crash Case #3 PDF has information about what is happening.
xah has is the debug file with the crash on line 960920


> AgentLogin application is crashing
> ----------------------------------
>
>                 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: Jeff Hoppe
>         Attachments: 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)