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

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

it looks like something that Greatel broke in their later firmware..  I noticed that the other unit i have has 1.1.4 firmware instead of 1.1.8 firmware in it..  and only produces 532 byte call-ID's..

however since the call-ID ends up in the from: I thought that was supposed to be 256 bytes are fewer..  here is the message from my other GT96 gateway unit..

my next step will be to run my system with those 2 GT96 gateways turned off and not on the network... I'll keep the debug version of asterisk running in case we incur a crash... 


���
^E^Sĩ^Sĩ^EN̯SUBSCRIBE sip:71210 at 192.168.10.5 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.247:5060
To: <sip:71210 at 192.168.10.5>
From: <sip:71210 at 192.168.10.5>;tag=378320-11548416-12719512-13889608-15059704-16229800-17399896-18569992-197391088-1109091184-1120791280-1132491376-1144191472-1155891568-1167601664-1179301760-1191001856-1202701952-1214402048-1226102144-1237812240-1249512336-1261212432-1272912528-1284612624-1296322720-1308022816-1319722912-1331423008-1343133104-1354833200-1
Call-ID: 378416082855-015481886282447-027191368128120-038892038939897-05059224884017-062291794765149-073991749955407-08569876383322-09739987854178-0109091385037277-0120791859558906-0132492119284435-0144192051290384-015589645800993-016760819425579-0179301486616912-019100113293689-0202701760402956-021440275984330-0226101234474419-0237811929897928-0249512006527564-026121300758673-027291682302795-028461913235084-029632152636217-030802615142828-0319721998370265-033142325416285-0343131562201018-0354831793834921-0 at InnaCall_Floor_3-6
CSeq: 4130 SUBSCRIBE
Max-Forwards: 70
Expires: 1200
Contact: <sip:71210 at 192.168.10.247:5060>
Accept: application/simple-message-summary
Authorization: Digest algorithm=MD5,nonce="27743c1d",realm="asterisk",response="e234465c91403416494d0aefdb3a97c0",uri="sip:71210 at 192.168.10.5",username="71210"
Event: message-summary
Content-Length: 0

                
> 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