[asterisk-bugs] [JIRA] (ASTERISK-21753) Seg Fault on incoming TCP SIP ACK

[Mathieu Boyer (JIRA)]

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

Mathieu Boyer updated ASTERISK-21753:
-------------------------------------

    Affects Version/s: 1.8.21.0
    
> Seg Fault on incoming TCP SIP ACK
> ---------------------------------
>
>                 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
>
>
> 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'm providing two exemples (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