[asterisk-bugs] [JIRA] (ASTERISK-23617) Asterisk segfault when AgentLogin concur in a time frame using Realtime ODBC

Matt Jordan (JIRA) noreply at issues.asterisk.org
Tue Apr 29 15:59:19 CDT 2014


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

Matt Jordan updated ASTERISK-23617:
-----------------------------------

    Assignee: Rusty Newton  (was: VoIPCamp)
      Status: Triage  (was: Waiting for Feedback)

> Asterisk segfault when AgentLogin concur in a time frame using Realtime ODBC
> ----------------------------------------------------------------------------
>
>                 Key: ASTERISK-23617
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23617
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_agent, Resources/res_odbc
>    Affects Versions: 11.8.1
>         Environment: CentOS release 6.5  2.6.32-431.5.1.el6.x86_64 Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz  12Gb RAM
>            Reporter: VoIPCamp
>            Assignee: Rusty Newton
>         Attachments: core.1014.gdb.txt, core.1014.log.txt, core.12979.txt, core.17055.gdb.txt, core.17055.log.txt, core.17381.txt, core.21046.txt, core.28334.gdb.txt, core.28334.log.txt, core.28596.gdb.txt, core.28596.log.txt, core.4930.txt, core.5904.txt, core.6580.gdb.txt, core.6580.log.txt
>
>
> Asterisk segfault when AgentLogin or logoff (hang up the chan_agent call) concur in a time frame. This use to happen when operation start or when agents shift is over. 
> Realtime ODBC is used for dynamic agents and parts of dialplan. I've isolated some backtraces which seems an issue with the odbc driver itself and not asterisk (even though think it should avoid to crash).



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



More information about the asterisk-bugs mailing list