[asterisk-bugs] [JIRA] (ASTERISK-24471) Crash - assert_fail in libc in pjmedia_sdp_neg_negotiate from /usr/local/lib/libpjmedia.so.2

[yaron nahum (JIRA)]

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

yaron nahum updated ASTERISK-24471:
-----------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

Hello Rusty,
I might have 2 versions of PJPROJECT. Initially I used version 2.1.0, and after I found the issue I have upgraded my lab and one of the live servers to 2.2.1. How do I know if both of them are running? which one the asterisk use?
I will send you the output you required on sunday.

> Crash - assert_fail in libc in pjmedia_sdp_neg_negotiate from /usr/local/lib/libpjmedia.so.2
> --------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24471
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24471
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip, Resources/res_pjsip
>    Affects Versions: 12.2.0, 12.6.1
>         Environment: centos 6
>            Reporter: yaron nahum
>            Assignee: yaron nahum
>            Severity: Critical
>         Attachments: backtrace_6_11_12_23.txt, backtrace.txt, yaron.debug.1
>
>
> We have had several crashes recent days on servers running 12.2.0rc1. We upgraded one of the servers to 12.6.1 and it crashed also. The crashes occur every couple of days per server.
> Our service uses AGI's for external logic. It also uses spandsp for fax receiving and sending.
> *** Yaron -
> Going over the debug messages I can see that the last call before the reboot was an incoming that was canceled in the same second of the initial INVITE. In between I can see that we activated a certain AGI, and then  after we got the cancel we jumped to h extension there we activated another AGI. 
> We are trying to simulated this scenario with SIPP and see if the reboot occurs. 
> One more thing I forgot to mention is that we have a lot of zombie processes running all the time related to Asterisk. It might be related to the reboot.



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