Summary:	ASTERISK-30034: re_invite rejected with 491 after update of session_media with its SDP
Reporter:	schovaers (mschovaers)	Labels:
Date Opened:	2022-04-27 07:51:49	Date Closed:	2022-05-11 12:00:01
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Resources/res_pjsip_session
Versions:	16.7.0	Frequency of Occurrence	Occasional
Related Issues:
Environment:		Attachments:
Description:	Asterisk sends INVITE with T38 udptl to A_party A_party sends 100 trying to Asterisk A_party sends re_invite with audio to Asterisk Asterisk handles the incoming sdp by clearing the previous session_media (session_media->handler->stream_destroy(session_media); so that session_media->udptl = NULL; Asterisk (pjilib) sends " 491 Another INVITE transaction in progres" Aparty sends 200 OK to the INVITE with T38 udptl Asterisk excutes "t38_reinvite_response_cb" then" t38_change_state" then ast_udptl_get_far_max_ifp  with a null pointer ==> Program terminated with signal SIGSEGV, Segmentation fault. #0  0x000056020ba28ab7 in ast_udptl_get_far_max_ifp (udptl=0x0) at udptl.c:1018 The re_invite has to be rejected without handling its SDP
Comments:	By: Asterisk Team (asteriskteam) 2022-04-27 07:51:49.984-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: Joshua C. Colp (jcolp) 2022-04-27 07:56:00.920-0500 It appears the bug you have submitted is against a rather old version of a supported branch of Asterisk. There have been many issues fixed between the version you are using and the current version of your branch. Please test with the latest version in your Asterisk branch and report whether the issue persists. Please see the Asterisk Versions [1] wiki page for info on which versions of Asterisk are supported. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions By: Joshua C. Colp (jcolp) 2022-04-27 08:01:30.287-0500 For example ASTERISK-29203 added code in later versions to check for the presence of udptl, so ensuring the issue isn't already fixed is needed. As well if it isn't then you'll need to provide a SIP trace[1] along with a backtrace[2]. [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information [2] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Asterisk Team (asteriskteam) 2022-05-11 12:00:01.131-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