| Summary: | ASTERISK-27376: Crash Asterisk chan_sip rtcp_mux | ||||
| Reporter: | Sebastian Gutierrez (sum) | Labels: | |||
| Date Opened: | 2017-10-28 11:56:26 | Date Closed: | 2017-11-08 08:56:27.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/chan_sip/General | ||
| Versions: | 13.17.0 13.18.0 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Ubuntu 16.04 | Attachments: | ( 0) core-brief.txt ( 1) core-brief.txt ( 2) core-full.txt ( 3) core-full.txt ( 4) core-locks.txt ( 5) core-locks.txt ( 6) core-thread1.txt ( 7) core-thread1.txt | ||
| Description: | Asterisk start crashing after changing to rtcp_mux=yes on chan_sip
tested updating to the newest relase candidate as with the previous version that was working with no crash without rtcp_mux | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-10-28 11:56:27.742-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Sebastian Gutierrez (sum) 2017-10-28 11:57:14.246-0500 attached core dump data By: Corey Farrell (coreyfarrell) 2017-10-29 17:53:09.074-0500 This may be a duplicate of ASTERISK-27205. By: George Joseph (gjoseph) 2017-10-30 07:52:20.211-0500 What happens if you compile without res_timing_timerfd (or use a "noload" statement in modules.conf)? Do you still get the crash? NOTE: You do need at least 1 timing interface like res_timing_dahdi or res_timing_phtread. By: Sebastian Gutierrez (sum) 2017-10-30 11:32:01.124-0500 I will try that and get back with the info By: Sebastian Gutierrez (sum) 2017-11-06 09:34:27.111-0600 dumped again with only dahdi timing By: Sebastian Gutierrez (sum) 2017-11-06 09:36:31.711-0600 dump info betterbacktraces dont optimize, only happens when rtcp mux is activated By: Sebastian Gutierrez (sum) 2017-11-08 09:07:57.060-0600 is there any way I can follow SWP-9959 ? By: Asterisk Team (asteriskteam) 2017-11-08 09:07:57.374-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Richard Mudgett (rmudgett) 2017-11-08 10:32:27.783-0600 No. SWP issues are used for internal issue prioritization. Any updates will be made on ASTERISK-27205. This issue is closed as a duplicate of ASTERISK-27205 issue. Follow the linked duplicate issue instead. | ||||