[Home]

Summary:ASTERISK-22003: Crash - signal 6, aborted - assertion failure in pjsip_auth_create_digest from /usr/lib/libpjsip.so
Reporter:Rusty Newton (rnewton)Labels:
Date Opened:2013-07-02 16:37:26Date Closed:2013-07-08 16:27:47
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Resources/res_pjsip
Versions:SVN Frequency of
Occurrence		Constant
Related
Issues:
Environment:trunk 393490Attachments:( 0) backtrace.txt
( 1) full.txt
Description:From what I can tell: If you set md5_cred to a non-hash-like value then Asterisk/pjsip isn't happy.

{noformat}
[auth6001]
type=auth
;auth_type=userpass
;password=6001
;username=6001
auth_type=md5
md5_cred=6001
username=6001
{noformat}

Will attach backtrace and full log up to crash.
Comments:By: Rusty Newton (rnewton) 2013-07-02 16:41:15.819-0500

backtrace shows some optimizations, but Asterisk is compiled with:
{noformat}
 Version:                     SVN-trunk-r393490
 Build Options:               DONT_OPTIMIZE, DEBUG_THREADS, LOADABLE_MODULES, BETTER_BACKTRACES, BUILD_NATIVE
{noformat}
By: Matt Jordan (mjordan) 2013-07-07 18:57:45.358-0500

I think you attached the wrong backtrace and log file - these appear to be from the ConfBridge CLI kick causes a crash issue.
By: Rusty Newton (rnewton) 2013-07-08 13:42:22.218-0500

Ugh. You are right. I need to sort out my crash/trace folders better. I'll get the right ones on here shortly.
By: Rusty Newton (rnewton) 2013-07-08 13:58:46.674-0500

attaching proper trace and log

After configuration and launching Asterisk, crash happens after calling inbound to Asterisk from the endpoint.