[asterisk-bugs] [JIRA] (ASTERISK-21806) Segfault in CHAN_SIP - in _int_malloc while in __ast_cc_config_params_init

[Christopher (JIRA)]

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

Christopher commented on ASTERISK-21806:
----------------------------------------

the pcap i attached at the end of it would be the SIP traffic right before the crash..  its a pcap of all the port 5060 traffic..  i set it up so that when asterisk core-dumped it stopped the tcpdump on 5060  so if you pull the last few lines of that it should be right before the crash. the pcap is the sip-0703* file in the list above..  that is the pcap that corresponds with the BT from 07-03 as well.. 

there are no phone calls running through the system, unless someone accidentially dials one of the DID's.. maybe those gateways are sending malformed messages? they didnt look abnormal when I looked at the pcap  but im also not completely up on the rfc to a T.


                
> Segfault in CHAN_SIP - in _int_malloc while in __ast_cc_config_params_init
> --------------------------------------------------------------------------
>
>                 Key: ASTERISK-21806
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21806
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.15.0
>         Environment: CPU: Atom D525, RAM 4GB, Fedora Linux, Kernel 2.6.43.8-1.i686
> 2 Aastra endpoints, 1 Polycom IP-650, 1 96 port SIP to analog gateway
> Asterisk 1.8.15-cert2
>            Reporter: Christopher
>            Assignee: Rusty Newton
>         Attachments: backtrace-0703-1958.txt, core-dump-maxx-052213.txt, sip-2013-07-03--19-57-00.pcap, valgrind-052213-1530.txt, valgrind-0523-1545-no-malloc.txt, valgrind-good-052213-1930.txt
>
>
> Segfault occurs whether system is idle or is in-use. it will crash within a day or two even if 0 calls are made on it.  running under safe_asterisk, results in multiple crashes within a few minutes until eventually system ends up in a MUTEX lock. over 3 gigs of RAM available and plenty of disk space at time of first crash. Possibly related to the 96 port gateway producing 96 SIP registrations all at once?

--
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