| Summary: | ASTERISK-29412: SIP and/or PJSIP Event Handling Stops | ||
| Reporter: | Josh Alberts (jalberts) | Labels: | |
| Date Opened: | 2021-04-30 16:27:27 | Date Closed: | 2021-05-16 12:00:01 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_pjsip Channels/chan_sip/General |
| Versions: | 16.17.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Linux cloud 4.15.0-111-generic #112-Ubuntu SMP Thu Jul 9 20:32:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux | Attachments: | ( 0) asterisk_dumps.zip |
| Description: | Since upgrading to 16.17.0, every few days it appears that chan_sip and/or chan_pjsip stop responding. In the debug logs I see events show up like a REGISTER coming into Asterisk, or an INVITE coming into Asterisk, but there is no response. The rest of the Asterisk core continues to function.
Essentially, no calls can be processed. Running sip reload fails to reload chan_sip. Restarting Asterisk seems to be the only solution. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2021-04-30 16:27:28.194-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Josh Alberts (jalberts) 2021-04-30 16:35:53.469-0500 Output of two separate runs of ast_coredumper By: Joshua C. Colp (jcolp) 2021-04-30 17:51:02.805-0500 The provided backtraces show no issue with chan_pjsip. They do show operations (chan_sip and dnsmgr) blocked waiting on DNS resolution to occur for various addresses. Is your DNS having issues? By: Josh Alberts (jalberts) 2021-05-01 08:50:02.258-0500 Yeah, unfortunately I didn't get a backtrace when the issue happened with pjsip. I'm back to 13.34.0 for the time being. I'm using 8.8.8.8 and 8.8.4.4 for DNS. I never had the issue on 13. I've ran Asterisk off this box with the same DNS servers for several years. By: Josh Alberts (jalberts) 2021-05-02 09:56:43.735-0500 It's happening back on 13.34.0, where it's never happened before. I just changed my DNS servers. By: Joshua C. Colp (jcolp) 2021-05-02 10:18:38.925-0500 Putting this into feedback pending results of changing DNS. By: Asterisk Team (asteriskteam) 2021-05-16 12:00:00.930-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||