| Summary: | ASTERISK-27203: res_pjsip_pubsub: Crash when sending request due to subscription timeout | ||
| Reporter: | Tony Guadagno (tonyg) | Labels: | |
| Date Opened: | 2017-08-16 18:36:06 | Date Closed: | 2020-01-14 11:14:02.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_pjsip_pubsub |
| Versions: | 13.17.0 | Frequency of Occurrence | One Time |
| Related Issues: | |||
| Environment: | freepbx 14.0.1.4 | Attachments: | ( 0) asterisk-ASTERISK-27203-results.tar.gz |
| Description: | hi, i issued a pjsip show contacts command and asterisk core dumped (attached). i was not able to reproduce this, so not sure if it is a real big issue...but...
| ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-08-16 18:36:06.943-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: Tony Guadagno (tonyg) 2017-08-16 18:38:39.160-0500 backtrace By: Joshua C. Colp (jcolp) 2017-08-22 07:09:25.742-0500 This appears to be a crash as a result of a subscription timeout, not a CLI command execution. Are you using TCP or TLS connections at all? By: Tony Guadagno (tonyg) 2017-08-22 07:14:38.570-0500 josh, yes, i am using sip-tls over tcp By: Rusty Newton (rnewton) 2017-08-25 17:25:03.084-0500 Have you been able to reproduce this since your last update? Ideally we'd like to get an Asterisk log showing what was going on when it happens. By: Asterisk Team (asteriskteam) 2017-09-09 12:00:02.802-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 | ||