[asterisk-bugs] [JIRA] (ASTERISK-21753) Seg Fault while attempting to queue AST_CONTROL_SRCCHANGE on a NULl channel when handling an incoming SIP ACK over TCP

Tue May 14 09:30:38 CDT 2013

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

Mathieu Boyer edited comment on ASTERISK-21753 at 5/14/13 9:30 AM:
-------------------------------------------------------------------

The log file includes VERBOSE & DEBUG (level 5)
It's a grep on string "C-000288ca"

We've got a REINVITE @ 13:14:52
[May 14 13:14:52] DEBUG[29928][C-000288ca] chan_sip.c: **** Received INVITE (5) - Command in SIP INVITE
And then a BYE @ 13:14:52
[May 14 13:14:52] DEBUG[26494][C-000288ca] chan_sip.c: **** Received BYE (8) - Command in SIP BYE
As I don't see BYE in the pcap from 192.168.69.10, I guess it comes from carrier side (not captured)

The last line in the log file is the last line written by asterisk before it crashed, then respawned thanks to safe_asterisk
[May 14 13:14:52] DEBUG[29928][C-000288ca] chan_sip.c: We're settling with these formats: (alaw)
[May 14 13:14:57] Asterisk 11.3.0 built by exploit @ vil-asterisk01 on a x86_64 running Linux on 2013-05-11 08:32:14 UTC

I just changed my tshark capture filter in order to get every SIP signaling (-f "port 5060")
I'll provide a full SIP trace @ next seg fault

Do you still need DEBUG/VERBOSE traces ?

      was (Author: thieums63):
    The log file includes VERBOSE & DEBUG (level 5)
It's a grep on string "C-000288ca"

> Seg Fault while attempting to queue AST_CONTROL_SRCCHANGE on a NULl channel when handling an incoming SIP ACK over TCP
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21753
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21753
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.21.0, 10.12.2, 11.3.0
>         Environment: Debian Wheezy
> Kernel 3.2.0-4-rt-amd64 #1 SMP PREEMPT RT Debian 3.2.41-2 x86_64 GNU/Linux
> Bi Xeon E5620 @ 2.40 Ghz
> 12 G RAM
>            Reporter: Mathieu Boyer
>         Attachments: backtrace1.txt, backtrace2.txt, crash1.pcapng, crash1.PNG, crash2.pcapng, crash2.PNG, crash3.log, crash3.pcapng, crash3.PNG
>
>
> Asterisk is performing pure SIP transit calls from/to an Avaya Communication Manager 5.2.1(ACM) from/to a SIP carrier (COLT).
> From an asterisk(192.168.69.9) point of view :
> - ACM(192.168.69.10) is SIP TCP PEER (as SIP UDP is not supported in this ACM release)
> - COLT(192.168.254.5 / 192.168.253.254) is a SIP UDP PEER
> directrtpsetup = yes
> This asterisk run around 300.000 calls per day
> Asterisk is crashing (seg fault) on similar SIP message (incoming SIP TCP ACK with session description, cseq = "2 ACK", from ACM).
> Crash frequency : between 0-2 per day.
> I can't reproduce the issue (i've generated with sipp the same scenario, it doesn't crash)
> I'm providing two exemples (11.3.0 bt, pcap file)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira