[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=206922#comment-206922 ] 

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

This morning i found a network issue, we found a duplicate IP on the network of the Asterisk server..  this has been resolved, and we will run the installation as it is t osee if this caused an issue..  my thoughts are an IP conflict could easily have caused issues with the machines TCP / IP stack  and of course the ARP tables..  which  very well might cause asterisk to corrupt and bomb.. in the meantime we have gone ahead and turned on Verbose and debug level 5 and are capturing it to a file.
                
> 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: Christopher
>         Attachments: core-dump-maxx-052213.txt, 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