Summary:	ASTERISK-26250: Asterisk crashes on unregister with PJSIP multi domain account
Reporter:	Norbert Varga (codwell)	Labels:
Date Opened:	2016-07-29 03:35:02	Date Closed:	2016-07-31 06:57:32
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_pjsip Resources/res_pjsip
Versions:	13.9.1	Frequency of Occurrence	Constant
Related Issues:
Environment:		Attachments:	( 0) backtrace.txt ( 1) error_log.txt
Description:	I have the following config in a config file included in pjsip.conf: {code} [1000@mypbx.com] type = endpoint transport = transport-udp-nat disallow = all allow = ulaw direct_media = no rtp_symmetric = yes force_rport = yes rewrite_contact = yes context = pbxtest auth = 1000 aors = 1000@mypbx.com from_domain=mypbx.com [1000] type = auth auth_type = userpass username = 1000 password = leo5t7h7CvEE [1000@mypbx.com] type = aor max_contacts = 1 remove_existing = yes {code} Registration seems OK with this account. But when I try to unregister, Asterisk crashes. In some cases it doesn't crash, but shows an error that "Object is likely destroyed" , see attachment. Backtrace also attached. If I remove the domain part from the AOR, unregister works just fine, no crashes: {code} [1000@mypbx.com] type = endpoint transport = transport-udp-nat disallow = all allow = ulaw direct_media = no rtp_symmetric = yes force_rport = yes rewrite_contact = yes context = pbxtest auth = 1000 aors = 1000 from_domain=mypbx.com [1000] type = auth auth_type = userpass username = 1000 password = leo5t7h7CvEE [1000] type = aor max_contacts = 1 remove_existing = yes {code} The problem with this I want to create other endpoints with the same username, like 1000@myotherpbx.com, and I have to use a different aor for that. And I cannot use an aor name different from the endpoint, because then I get "AOR not found for endpoint" error.
Comments:	By: Asterisk Team (asteriskteam) 2016-07-29 03:35:04.047-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: Joshua C. Colp (jcolp) 2016-07-29 04:52:38.331-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 In fact the code in the backtrace doesn't even exist anymore in 13.10.0, as it was removed and redone. By: Norbert Varga (codwell) 2016-07-29 04:59:46.193-0500 Thank you for the quick response! I'm going to try the 13.10.0. Please confirm that the PJSIP config above is correct and I can use it in 13.10.0. Thanks! By: Joshua C. Colp (jcolp) 2016-07-29 05:01:26.589-0500 There's never any changes done in a release branch which would result in a subsequent release being incompatible, but there's been no work done on multi-domain support in 13.10.0 either. By: Norbert Varga (codwell) 2016-07-31 06:53:47.261-0500 It seems register/unregister works for multidomain accounts in 3.10.0!