Summary:	ASTERISK-30124: res_pjsip_outbound_registration: reload causes assertion in devmode and DO_CRASH
Reporter:	N A (InterLinked)	Labels:
Date Opened:	2022-07-04 09:15:29	Date Closed:
Priority:	Minor	Regression?
Status:	Open/New	Components:	Resources/res_pjsip_outbound_registration
Versions:	18.9.0	Frequency of Occurrence	One Time
Related Issues:
Environment:		Attachments:	( 0) pwg2fjegpe.txt
Description:	* Note that devmode and DO_CRASH must be enabled for the crash to happen. What happened was I commented out some sections in pjsip.conf for a defunct registration that is no longer used. Specifically, this was what I commented out, and the only change between the reload: {noformat} [reg_losangeles1.voip.ms] type = registration retry_interval = 20 max_retries = 10 contact_user = REDACTED expiration = 120 transport = transport-udp outbound_auth = auth_reg_losangeles1.voip.ms client_uri = sip:REDACTED@losangeles1.voip.ms server_uri = sip:losangeles1.voip.ms [auth_reg_losangeles1.voip.ms] type = auth password = REDACTED username = REDACTED [REDACTED] type = aor contact = sip:losangeles1.voip.ms qualify_frequency = 60 [REDACTED] type = identify endpoint = REDACTED match = losangeles1.voip.ms [REDACTED](endpoint) context = REDACTED dtmf_mode = inband aors = REDACTED {noformat} When I did "pjsip reload", that then triggered an assertion. I think the above is relevant because PJSIP was trying to do something with the stuff above and that was what got removed on the reload. Backtrace attached.
Comments:	By: Asterisk Team (asteriskteam) 2022-07-04 09:15:31.198-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: N A (InterLinked) 2022-07-04 09:18:26.734-0500 Backtrace By: Joshua C. Colp (jcolp) 2022-07-04 10:24:03.445-0500 This is an assertion, which happened because you're in developer mode. In a non-developer build the assertion would be turned into a return and things would continue onward. By: Benjamin Keith Ford (bford) 2022-07-05 11:26:30.868-0500 Can you confirm crash does not happen outside of developer mode and report back? By: N A (InterLinked) 2022-07-05 14:21:06.629-0500 Sorry, I should have more specific - the crash was caused by the assertion as Josh pointed out, specifically as DO_CRASH was enabled on this system. So this would only happen in developer mode with DO_CRASH enabled. There's definitely still a bug here but it wouldn't cause a crash in a normal build. By: Benjamin Keith Ford (bford) 2022-07-07 08:15:21.668-0500 Thanks for the additional info. I'll go ahead and open up an issue for it.