| Summary: | ASTERISK-14219: Crash in INVITE with replaces | ||
| Reporter: | Loris Santamaria (loris) | Labels: | |
| Date Opened: | 2009-05-28 12:47:40 | Date Closed: | 2009-06-01 09:05:49 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) backtrace ( 1) full | |
| Description: | Hi, we are using sip style call pickup with snom phones, and we' ve tried with the patches that are floating around (like the one in issue 5014) with good results. However in one setup, the call pickup produces a segfault in asterisk almost 75% of the times. We have reproduced the issue with asterisk 1.4.22, 1.4.23, 1.4.24, 1.4.25-rc1 and with three different patches for implementing call pickup with snom phones. I have the suspicion that in this setup the sip t1 timer of the phones is too low, the phone retransmits the "INVITE with replaces", and the retransmission causes the crash. I'll try to test with a bigger T1 timer to see if the problems goes away. Yet that won't be an ideal solution because a slow link between the phone and asterisk or temporary congestion in the server could still require a retransmit from the phone and could trigger the crash. Attached you'll find a backtrace, asterisk log with debug enabled, and the patches we've used in our tests. | ||
| Comments: | By: Loris Santamaria (loris) 2009-05-28 13:01:37 Ok i couldn't upload the patches because I didn't write them. FYI, the asterisk used to reproduce the issue has only the patch referenced in issue 5014 applied: https://issues.asterisk.org/file_download.php?file_id=20223&type=bug By: Loris Santamaria (loris) 2009-05-28 17:45:08 The phones had a sip t1 timer of 100ms. With the default setting of 500 ms I can't reproduce the crash anymore. Haven't tried on a slow link nor with a heavy call load. By: Joshua C. Colp (jcolp) 2009-06-01 09:05:48 I'm sorry but we do not support patched versions of Asterisk here. If you can reproduce the issue using the supported version with Snom pickup support then we can track it down there and fix it. | ||