| Summary: | ASTERISK-18949: Segmentation fault in chan_sip.c (SIP/TLS SRTP configuration) | ||
| Reporter: | Thomas Arimont (tomaso) | Labels: | |
| Date Opened: | 2011-12-01 07:00:04.000-0600 | Date Closed: | 2012-01-23 13:16:48.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/TCP-TLS |
| Versions: | 1.8.8.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | 1.8.8.0-rc4, i586 | Attachments: | ( 0) backtrace_seg_fault.log |
| Description: | While examing an error (segfault) in SRTP (probably related to issue ASTERISK-16665) we detected another seg fault in chan_sip.c in a SIP/TLS SRTP test environment (using SNOM 360 and Tiptel SIP phones). Enclosed the backtrace log. | ||
| Comments: | By: Leif Madsen (lmadsen) 2011-12-01 14:04:27.456-0600 Which OS was this reported against? I ask because I saw another issue reported for Mac OSX. By: Thomas Arimont (tomaso) 2011-12-01 22:30:32.080-0600 Linux (OpenEmbedded), i586 By: Mark Michelson (mmichelson) 2012-01-11 12:40:03.549-0600 I have been trying to reproduce this locally but I am unable to. I assume since the crash is in a malloc() call that this is not something you can reliably reproduce, but I can at least get a feel for what type of system this is. Is this system heavily loaded? About how many peers do you have on it? How many calls does this system handle at a time? How often does this crash occur? If you have it, can you post a log of Asterisk's messages shortly before the crash occurred? I'm trying to figure out what was happening at the time and also trying to find out if there were any error messages. Thanks! By: Thomas Arimont (tomaso) 2012-01-12 05:02:02.749-0600 Mark, unfortunately the backtrace is the only thing I can give you right now since I cannot reproduce the issue in the moment.AfaIk the system was not heavily loaded. Max 10 SIP peers registered/registering, not more than 5 concurrent calls. I will advise our test department to take a further look to this problem and to provide more information if the seg fault takes place another time. If you feel more comfortabe with it, please suspend this issue until we provide new information for you. By: Mark Michelson (mmichelson) 2012-01-23 13:16:48.280-0600 Closing as "Cannot Reproduce." | ||