[asterisk-bugs] [JIRA] (ASTERISK-24633) Asterisk crashing (awaiting backtrace)

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-24633:
-----------------------------------------

In addition, be sure to follow this guide as well: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information and provide the resulting log. The log should include all of the logger channels detailed.

The log should correspond with the next backtrace that you provide. That means, the log should have been captured at the same time as Asterisk was running up until the crash. At that point, provide the logs and a backtrace from the *core* file that Asterisk dumps.

> Asterisk crashing (awaiting backtrace)
> --------------------------------------
>
>                 Key: ASTERISK-24633
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24633
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 11.15.0, 13.1.0
>         Environment: CentOS 6.5 64bit
>            Reporter: Sid Mason
>            Assignee: Sid Mason
>            Severity: Critical
>         Attachments: DEBUG_LOG Asterisk 11.15.txt, DEBUG_LOG.txt
>
>
> It seems asterisk erases the information about the ongoing call through Chan_SIP 
> This happens when :
> A) This is right before the time Asterisk looses all SIP Dialog status related second leg on Bridges
> Dec 23 03:29:24 callback01my kernel: asterisk[2652]: segfault at 9d0 ip 000000000048c120 sp 00007f9463ffc858 error 4 in asterisk[400000+208000]
> Note:  At above point asterisk uptime 'core show uptime' is reset to zero, but strangely asterisk recover or continue to operate.
> B) 20 or AMI listener is attached to asterisk on port 5038 and they all have filter as below:
> C) AMI has filter of the UNIQUE ID of the channels and others:
> '!Event: AGIExec'
> '!Event: VarSet'
> '!Event: RTCPSent'
> '!Event: RTCPReceived'
> '!Event: VarSet'
> D) the call durations are usually above 10 minutes
> E) the bridge is doing unlink before the hang-up and somehow asterisk must hold the information for SIP Dialog right before the hang-up
> I tried asterisk 11.15 and the same result was there.
> At this point ANSWEREDTIME is reported as NULL as well
> F) At incident asterisk is loosing track of multiple calls at once.



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