[asterisk-dev] Asterisk Segfault After PJSIP Commit 5241
Ross Beer
ross.beer at outlook.com
Tue Mar 1 11:29:27 CST 2016
Hi George,
I have now got asterisk 13 trunk, however loading is very slow. This is due to asterisk reading all of the realtime Sorcery peers and marking them all as 'Unknown'. Is there a way to only cache peers that have tried to register?
So far its taking 20 mins to load!!
Also asterisk has the following warning:
taskprocessor.c:803 taskprocessor_push: The 'subm:ast_device_state_topic-000055d0' task processor queue reached 500 scheduled tasks.
Neither were issues in the previous release.
Thank you for your assistance,
Ross
From: george.joseph at fairview5.com
Date: Tue, 1 Mar 2016 09:08:37 -0700
To: asterisk-dev at lists.digium.com
Subject: Re: [asterisk-dev] Asterisk Segfault After PJSIP Commit 5241
On Tue, Mar 1, 2016 at 5:58 AM, Ross Beer <ross.beer at outlook.com> wrote:
Further to my previous email it appears this bug won't be easily resolved by changing the method:
pjsip_dlg_create_uas() >> pjsip_dlg_create_uas_and_inc_lock().
Asterisk starts ok, allows registrations but no calls progress.
You have to pull Asterisk from the 13 branch. This should have been fixed with review 2236 and I've been running with that patch and pjproject trunk.
From: ross.beer at outlook.com
To: asterisk-dev at lists.digium.com
Date: Tue, 1 Mar 2016 11:49:55 +0000
Subject: Re: [asterisk-dev] Asterisk Segfault After PJSIP Commit 5241
I've just found an open issue for this https://issues.asterisk.org/jira/browse/ASTERISK-25751
From: ross.beer at outlook.com
To: asterisk-dev at lists.digium.com
Date: Tue, 1 Mar 2016 11:06:09 +0000
Subject: [asterisk-dev] Asterisk Segfault After PJSIP Commit 5241
Hi,
Since PJSIP Commit 5241 (https://trac.pjsip.org/repos/changeset/5241) Asterisk crashes when a device registers.
The commit resolves the following:
• Crash when endpoint has multiple worker threads and SIP TCP transport is disconnected during incoming call handling.
• Deprecated pjsip_dlg_create_uas(), replaced by pjsip_dlg_create_uas_and_inc_lock().
• Serialized transaction state notifications (of 'terminated' and 'destroyed') in case of transport error.
This commit should resolve a previous segfault within Asterisk, however due to the deprecated method I believe this is causing an additional issue.
Can this be easily resolved to resolve both segfaults?
Kind regards,
Ross
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20160301/900710ec/attachment-0001.html>
More information about the asterisk-dev
mailing list