| Summary: | ASTERISK-29944: Bundled PJSIP 2.12 | ||||
| Reporter: | Morten Sølvberg (Soelvberg) | Labels: | |||
| Date Opened: | 2022-03-03 08:38:18.000-0600 | Date Closed: | 2022-03-03 08:46:28.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | pjproject/pjsip | ||
| Versions: | 18.0.1 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | We are periodically experiencing a crash in PJSIP v. 2.10, that I can see is fixed in PJSIP 2.12.
We however are having problems upgrading the bundled version. Really not a straight forward job... Do you have any plans to release a new Asterisk 18 build with the bundled PJSIP version 2.12 in the foreseeable future? According to this, you probably should: https://threatpost.com/rce-bugs-popular-voip-apps-patch-now/178719/ We are however not impacted by this, since we are not using PJSUA, but I imagine that there will others with same request. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2022-03-03 08:38:20.532-0600 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: Asterisk Team (asteriskteam) 2022-03-03 08:38:20.919-0600 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Joshua C. Colp (jcolp) 2022-03-03 08:42:05.361-0600 There is already an issue[1] open for 2.12, as well as reviews up. We're also investigating all security fixes as part of 2.12 and seeing what needs to be backported in the mean time. [1] ASTERISK-29351 By: Asterisk Team (asteriskteam) 2022-03-03 08:42:13.360-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. | ||||