[asterisk-bugs] [JIRA] (ASTERISK-24471) Asterisk Crash

[yaron nahum (JIRA)]

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

yaron nahum commented on ASTERISK-24471:
----------------------------------------

While investigating this issue and comparing all the debug and core files taken during the crashes, I found that there is one  scenario that seems to be repeating:
- In all the core files the following routine was involved :
#9  0x00007f5205293741 in answer (data=0x7f52118e1708) at chan_pjsip.c:454
        status = <value optimized out>
        packet = 0x7f5210fa9fe8
        session = 0x7f52118e1708d)
        __PRETTY_FUNCTION__ = "answer"
- In all the debug taken just before the crashe happened the following message appeared:
Hangup of channel PJSIP/KAMnet_CBS-0000b5d3 detected in answer routine
 - Only before the crash this message was generated after a CANCEL message was received (in other cases BYE message was received).

It seems to me that there is a bug related to the case where a call in being answered (Answer function in the dialplan), and while handling the answer a CANCEL is received (before the 200OK is sent).
I haven't been able to reproduce this issue.

Hope that someone would look at it soon.


> Asterisk Crash 
> ---------------
>
>                 Key: ASTERISK-24471
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24471
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 12.2.0, 12.6.1
>         Environment: centos 6
>            Reporter: yaron nahum
>            Severity: Critical
>         Attachments: 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)