| Summary: | ASTERISK-28506: asterisk crashes at random frequent intervals | ||||
| Reporter: | Serge (zeusca) | Labels: | |||
| Date Opened: | 2019-08-19 10:07:00 | Date Closed: | 2019-09-05 11:17:38 | ||
| Priority: | Critical | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/chan_pjsip | ||
| Versions: | 16.5.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Asterisk acting as bare bone B2B for topology hiding and media transcoding, SIP proxies in front and back | Attachments: | ( 0) core-brief.txt ( 1) core-full.txt ( 2) core-locks.txt ( 3) core-thread1.txt | ||
| Description: | Scenario:
Some SIP proxy sends calls to Asterisk with different foreign RURI domains. Asterisk must retain the full RURI user@domain and dial it out via another outbound_proxy. Dialplan (a single line): {noformat} exten => _X.,1,Dial(PJSIP/lb1/sip:${EXTEN}@${SIPDOMAIN}) {noformat} Where 'lb1' endpoint has parameter: {noformat} outbound_proxy=sip:lb1.mydomain.com\;lr {noformat} All works fine until Asterisk crashes at frequent random intervals (10-60 minutes) under some call load increase. Thanks. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2019-08-19 10:07:01.269-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]. 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. By: Serge (zeusca) 2019-08-19 10:10:12.786-0500 backtraces of crash | ||||